DECHY logo

Ctrl K or / to search, arrows to move, Enter to open

Cloud platform

Microsoft Azure

Azure is the cloud that fits most naturally into a Microsoft organization: the same sign-in, the same security tooling, and close ties to Microsoft 365 and Windows. We build and run applications on it, and we compare it with other clouds where the fit is less obvious.

  • 1,200+ clients helped
  • Building since 2010
  • 15 services, one team
  • 50+ technologies

At a glance

What it is

Azure is Microsoft's cloud platform, offering rented servers, databases, and many other services that work closely with Microsoft 365, Windows, and Microsoft's identity tools.

What it means

Microsoft's cloud, built to join its other tools

Azure is Microsoft's cloud platform. Like other clouds it rents computing, storage, and databases by use. Its distinctive strength is how closely it works with Microsoft's own identity, productivity, and developer tools.

For an organization that already signs everyone in through Microsoft, applications on Azure can use the same accounts, groups, and security policies. That removes a whole layer of work and a whole class of mistakes.

It is also a natural home for applications built on Microsoft's own technologies. For other workloads it competes on price and features with the other large clouds, and we compare them honestly.

A rack of servers in a server room

Alternatives

Azure compared with other clouds

Azure compared with other cloud options
ConsiderationWhere Azure helpsWhere to check
Microsoft identity and tools Native links to Entra ID and Microsoft 365. Little advantage if you do not use them.
Windows and SQL Server workloads Strong support, including licensing options. Licensing can be complex, so we model the costs.
Other workloads A broad range of services comparable to other clouds. Compare price and skills against AWS and Google Cloud.
Hybrid set-ups Good tools for connecting offices and data centers. Network design needs care.

Choosing the right approach

Licensing needs attention

Microsoft's licensing can make the same workload cost very different amounts depending on what you already own and how you run it. A design that ignores licensing can be wrong by a wide margin.

We model costs with your existing licenses in mind, and confirm current terms with Microsoft or your reseller, since they change.

Where it fits

Moving Windows-based systems to Azure

A common path for organizations with servers in an office or data center.

Moving Windows-based systems to Azure

A sequence of 5 steps. Inventory: Servers, databases, and who depends on them.; Decide the route: Move as is, update, or replace each system.; Prepare the foundation: Network, identity, and security set up first.; Move in stages: Least risky first, testing each.; Run and improve: Monitor, optimize cost, and retire the old servers..

  1. InventoryServers, databases, and who depends on them.
  2. Decide the routeMove as is, update, or replace each system.
  3. Prepare the foundationNetwork, identity, and security set up first.
  4. Move in stagesLeast risky first, testing each.
  5. Run and improveMonitor, optimize cost, and retire the old servers.
This diagram shows five steps in moving systems to Azure, from taking inventory to running the new set-up and retiring the old servers.

Typical uses

Workloads that suit Azure

  1. Business applications for Microsoft organizations

    Internal tools and portals that use staff sign-in and share data with Microsoft 365.

  2. Moving Windows and SQL Server systems

    Servers and databases lifted from an office or data center, then improved in stages.

  3. Applications built on Microsoft technologies

    Software written in .NET, hosted with the tools its developers already know.

  4. Hybrid arrangements

    Some systems staying on site while others move, joined by a secure network.

What DECHY can do

Working with Azure

Design

  • Architecture matched to your Microsoft estate.
  • Cost and licensing estimates.

Build and migrate

  • New applications on Azure services.
  • Staged moves of servers and databases.

Secure

  • Sign-in and access tied to your Microsoft accounts.
  • Policies and monitoring across subscriptions.

Run

  • Releases through Azure DevOps (Microsoft's tool for planning and releasing software) or GitHub Actions.
  • Monitoring, alerts, and cost reviews.

Common questions

Questions about Azure

Do we need Azure if we use Microsoft 365?

Not necessarily. Microsoft 365 runs without it. Azure becomes worthwhile when you have applications, servers, or data to host and want them to share your Microsoft sign-in.

Can you move our Windows servers?

Yes, in stages, after an inventory. Some are best moved as they are, some updated, and some replaced.

Is Azure only for .NET?

No. It runs many languages and frameworks, including Python, Java, and JavaScript, as well as Microsoft's own.

Who manages it day to day?

That is agreed at the start. We can run it, support your team, or hand it over with documentation.

Have a different question?

Tell us what you are weighing up and we will answer it plainly.

Ask a question

Already a client? Email support@dechytech.com

Technical depth

How we build with Azure

What we settle early on Azure work: structure and governance, running applications, and operations, so nothing surprises your team later.

We organize subscriptions under management groups, apply policy and role-based access consistently, and describe environments in code with Terraform or Bicep.

Tell us which Microsoft tools you rely on

Describe your servers, your sign-in set-up, and what you want to run in the cloud. We will propose an Azure design and a cost range.