Microsoft Azure
Microsoft Azure is Microsoft’s cloud platform: virtual machines, databases, storage and network services delivered on a pay-as-you-go basis. For many Italian companies it is the shortest route, because the working environment is already Microsoft – identity, email, files, applications on Windows Server – and Azure is its natural continuation. Aesir designs, sizes and manages it, keeping cloud, network and workstations together.
Microsoft Azure at a glance
Pay-as-you-go infrastructure
Virtual servers, disks, networks and databases are created when needed, at the size needed, and changed when requirements change. Instead of buying hardware every four or five years there is a recurring cost tied to actual use. The renewal cycle, with its spending peaks and downtime, disappears.
Continuity with the Microsoft environment
If the company already uses Microsoft 365, users and groups are the same: the Entra ID identity applies to email, files and access to resources in Azure. This simplifies conditional access rules, multi-factor authentication and offboarding, because a person is disabled in one place only.
Virtual servers and managed services
Existing servers can be moved to the cloud almost as they are, or some parts can be replaced with services run by the platform: managed SQL databases, file storage, web applications. The first route is faster, the second removes maintenance over time. In practice both are used, for different parts of the same system.
Continuity and recovery
Azure offers tools to replicate machines and data to another geographic area and to restart in case of disaster, in addition to ordinary backup. It is often why a company with a single server room decides to look at the cloud: building a second physical site costs far more than keeping one ready elsewhere.
Where data resides
There are Azure regions in Italy and other European countries, and the region is chosen at design stage. Microsoft has also defined an EU Data Boundary for its cloud services, designed to keep the storage and processing of customer data within the Union. It is a topic we cover extensively in Digital sovereignty.
Licences and costs
Spending depends on resources running, traffic and licences. Some mechanisms have a big impact: term commitments on always-on machines, scheduled shutdown of test environments, reuse of Windows Server licences already owned. They must be assessed case by case, otherwise the bill grows without anyone noticing.
Microsoft Azure features
In most SME projects Azure is used for three things: hosting application servers that today sit in the machine room, keeping data with reliable backup and restore, and providing a restart point if the office becomes unusable. Around this core, when needed, come a virtual desktop for people working off site or on non-company devices, a managed database instead of an SQL instance to maintain, and integration with the identity already in use. The architecture stays understandable: few components, each with a reason.
On jurisdiction it is best to state things as they are, without alarmism. Data can be hosted in European regions and Microsoft has made public commitments on keeping the storage and processing of its cloud customers’ data in Europe. At the same time Microsoft is a US company and remains subject to US law, including the CLOUD Act, which allows US authorities to approach a company under their jurisdiction even for data stored abroad. The provider publishes contractual commitments on how it handles and challenges these requests, and there is a data transfer framework between the European Union and the United States. The practical conclusion is not “use it” or “do not use it”, but: classify data, decide which can sit there, encrypt sensitive data with customer-controlled keys and record it in the processing register. The full reasoning is in Digital sovereignty.
- Virtual machines: Windows and Linux servers of different sizes, with managed disks and the option to resize or switch off according to actual use.
- Virtual networks and office connection: subnets, traffic rules and encrypted tunnels to the company network, so the cloud stays an extension of the LAN and not an exposed island.
- Identity with Entra ID: single users for cloud and workstations, multi-factor authentication, access conditioned on device and context, separate admin privileges.
- Azure Backup: scheduled copies of machines, files and databases with defined retention rules, and restores tested periodically instead of taken for granted.
- Replication and disaster recovery: continuous copy of machines to another area, with a documented restart procedure tested in a test environment.
- Managed databases: SQL instances and other engines run by the platform, with updates, backups and high availability handled by the provider.
- Storage: space for files, objects and historical archives with different cost tiers for data used daily and data that only needs keeping.
- Virtual desktop: Windows sessions delivered from the cloud, useful for external collaborators, temporary sites or applications you do not want to install on every machine.
- Monitoring and activity log: metrics, alerts and a trail of admin operations, to act before the user reports the problem.
- Region choice: the geographic location of resources is a design decision, declared and verifiable in the configuration.
How we put it into operation
The starting point is an inventory of what exists and how it is used: which servers support which processes, how long downtime can last before work stops, how much data there is and how it is protected today, which applications have licensing or compatibility constraints. On this basis we decide what to move, at what size, in which region, with which backup and restore plan and which spending profile. We also say what to leave where it is: some workloads still make more sense on site, and a project that recognises this at the start avoids costs discovered later.
Implementation proceeds in agreed phases, with migrations in shared windows and the option to fall back until the new environment is stable. From then on the work is ongoing: updates, access control, monitoring, real restore testing, periodic review of sizing and spending, daily user support. The customer has one contractual point of contact for platform, network and workstations, instead of coordinating different suppliers when something does not add up.
Microsoft Azure is part of Cloud and Infrastructure. See also the Aesir method and our success stories.
Want to know whether Microsoft Azure makes sense for your company?
We start from the process, not the product. A first meeting with no commitment.