Azure in Morocco: when to move to the Microsoft cloud and which costs to plan for

The short answer: moving to Azure makes sense in Morocco when a server reaches end of life and replacing it is no longer justified, when a business application must be reachable from several sites or by remote staff, or when you need a recovery site without renting a second office. It is not a default choice: a recent, stable server used only at the office is often cheaper to keep on premises. You should also know that there is no Azure region in Morocco: your data will be hosted in Europe, which has consequences under Moroccan law 09-08.

On budget, Azure is pay-as-you-go, and that is exactly what surprises businesses: the bill is not a flat fee but the sum of several meters (compute, disks, backups, outbound data, licences) and the commitment model you choose. This guide explains when to move to the Microsoft cloud, what really makes up the bill, how to estimate it before signing and how to keep it under control afterwards. We give no amounts: they depend on your inventory, the region and the exchange rate, and they change regularly.

At ALLSAFE SOLUTIONS, a Microsoft partner based in Casablanca, we supply Azure subscriptions to businesses, with or without migration, and we administer them for those who want it through our Azure and Microsoft 365 in Morocco offering.

Azure in Morocco: where will your data live?

As of publication, the official list of Azure regions published by Microsoft has no region in Morocco. The closest publicly available regions are in Europe:

Azure region	City	Availability zones	Note
France Central	Paris	Yes	Paired with France South, restricted access
Spain Central	Madrid	Yes	No paired region
West Europe	Netherlands	Yes	Paired with North Europe (Ireland)
Germany West Central	Frankfurt	Yes	Paired with a restricted-access region
Italy North	Milan	Yes	No paired region

Source: list of Azure regions, Microsoft Learn documentation. The region is chosen on three criteria: latency from your sites in Morocco, which we measure before deciding; availability of the services you need, since not every service is offered everywhere; and the legal framework that applies to your data.

That last point is not a detail. Hosting personal data about customers or employees outside Morocco is a transfer under law 09-08, governed by its articles 43 and 44. We cover the steps in our article on law 09-08 and the CNDP. If a constraint requires hosting in Morocco, the alternative is a local datacenter, compared in hosting servers in a datacenter in Morocco.

When to move to the Microsoft cloud (and when to wait)

Azure is not an automatic replacement for your server room. Here are the situations where we recommend it, and those where we advise waiting.

Situation	Azure relevant?	Why
Server out of warranty, light application	Often yes	Avoids buying a server, a UPS and a new hardware-bound licence
Business application used from several cities	Yes	One access point, without routing every site through head office
Need for a recovery site	Yes	Azure Site Recovery replicates servers and lets you start them in Azure after a disaster
Remote desktops for contractors or home workers	Yes	Azure Virtual Desktop publishes Windows desktops and apps from Azure
Recent, stable server used only at the office	Rather not	It is already paid for; a monthly Azure bill would be added for no gain
Large file volumes constantly read over the internet	With care	Outbound data is billed and can dominate the bill
Single, fragile internet link	Not yet	If the link drops, the servers are unreachable: add a second link first

The last point is the one most often forgotten. Once your servers are in the cloud, your internet connection becomes a critical part of production. Before any migration, we check the main link, the backup link and the firewall; see our guide to business fibre in Morocco.

The Azure services an SMB actually uses

The Azure catalogue has hundreds of services. For a Moroccan SMB, a handful covers the vast majority of projects:

• Virtual machines: your current Windows or Linux servers, moved as they are. The simplest way in.
• Azure Files: managed file shares over SMB, with no file server to maintain.
• Azure Backup: backup of Azure virtual machines and of servers that stay on premises.
• Azure Site Recovery: server replication for disaster recovery.
• Azure Virtual Desktop: published Windows desktops for remote users.
• Microsoft Entra ID: the identity directory already used by Microsoft 365, which also controls access to Azure, with MFA and conditional access.

If you already use Microsoft 365, you already have a tenant and an Entra ID directory: the Azure subscription attaches to it, so there is no second account system to manage.

Costs to plan for, meter by meter

Azure bills by usage. Understanding the meters is the best protection against surprises.

Cost item	What drives it	Common trap
Compute (virtual machines)	Machine size, running hours, region	A machine shut down from Windows but not deallocated is still billed
Managed disks	Type (Standard HDD, Standard SSD, Premium SSD, Premium SSD v2, Ultra) and provisioned size	Disks are billed on provisioned size, not used space, even when the machine is deallocated
Backup and snapshots	Protected volume, retention, number of copies	Long retention never reviewed, forgotten snapshots
Outbound data	Volume sent from Azure to the internet or another region	Inbound data is free, outbound is not: a busy file server accessed from the offices costs bandwidth
Licences	Windows Server, SQL Server, Remote Desktop	Paying twice for a licence you already own by not enabling Azure Hybrid Benefit
Networking	VPN gateway, public IP addresses, load balancer	The VPN gateway is billed continuously, even with no traffic
Support and operations	Microsoft support plan, managed service provider	Forgetting that someone must monitor, patch and back up

For disks, Microsoft offers five types: Standard HDD for backup and infrequent use, Standard SSD for web servers and lightly used applications, Premium SSD for production, Premium SSD v2 and Ultra for demanding databases. An SMB file server almost never needs the last two.

Pay-as-you-go, reservations or savings plan

The same server can cost very differently depending on how you buy it. Microsoft offers three main models:

Model	Commitment	Best for
Pay-as-you-go	None, cancel anytime	Tests, short projects, irregular workloads, the first period after migration
Reservations	One or three years, on a machine type in one region	Stable servers running around the clock
Savings plan for compute	One or three years, on an hourly compute spend	Changing workloads, several machine families or regions

Microsoft recommends a clear order: first remove and right-size anything unused or oversized, only then buy commitments. A reservation on an oversized machine locks in the waste for one or three years. That is why we always start on pay-as-you-go, measure real consumption during the first weeks, then propose commitments.

Two levers complete the picture:

• Azure Hybrid Benefit: if you hold eligible Windows Server or SQL Server licences, you can reuse them in Azure instead of paying for the licence included in the machine price. We check your rights before migrating; see our guide to Windows Server 2025 licensing and CALs.
• Scheduled shutdown: a test or training server used only during office hours can be deallocated at night and at weekends.

How to estimate the bill before signing

A migration is not decided on gut feeling. Microsoft provides two official tools that we use every time:

1. Azure Migrate assesses your current servers: it checks whether they can be migrated, recommends a virtual machine size based on their real usage, then produces a cost estimate.
2. The Azure pricing calculator lets you build the complete solution (machines, disks, backup, networking, outbound data) and compare purchase models.

The estimate is only as good as the inventory: servers, roles, data volumes, number of users, traffic between sites, applications that talk to each other. That is the job of the initial audit, described in IT audit for an SMB. We also set the cost of the on-premises option over the same period alongside it, for an honest comparison.

Keeping the bill under control once on Azure

Microsoft Cost Management is included with Azure and tracks spending. The settings we apply to every subscription:

• Budgets and alerts: a monthly budget with several alert thresholds, sent to the business owner and to our team.
• Tags: every resource carries its application and department, so you know who consumes what.
• Azure Advisor: it spots underused machines and suggests resizing or shutting them down.
• Monthly review: orphaned disks, old snapshots, unused IP addresses, machines left running.

These checks are part of our monthly operations report, along with subscription security: mandatory MFA, separate admin accounts, admin access not exposed to the internet. On that last point, see our guide to rolling out MFA in a business.

Migrating to Azure: the five-step method

1. Inventory and assessment: servers, applications, dependencies, volumes, with Azure Migrate.
2. Region and legal framework: measured latency, available services, law 09-08 compliance.
3. Foundations: subscription, virtual network, VPN or secure access from your sites, identities, backup, budgets.
4. Migration in waves: one pilot server, then the rest, each cutover planned outside production hours with a rollback path.
5. Operations and optimisation: monitoring, patching, tested backup, then commitments once consumption has stabilised.

Not every business moves everything. Many keep a local server and use Azure as a recovery site, which ties in with our disaster recovery plan for SMBs. Others prefer a private cloud on Proxmox; see migrating from VMware to Proxmox.

Mistakes we fix on Azure

1. Machines stopped but not deallocated, billed as if they were running.
2. Orphaned disks and snapshots left behind after a machine is deleted.
3. Windows Server licences paid twice, because Azure Hybrid Benefit was not enabled on eligible licences.
4. A reservation bought on day one on an oversized machine.
5. Remote Desktop exposed directly to the internet instead of a VPN or secure access.
6. No budget or alert, so the drift is only discovered on the invoice.
7. A single internet link at head office, which makes cloud servers unreachable at the first outage.

Checklist before moving to Azure

• Inventory of servers and applications, with their real usage.
• Applications compatible, and vendors agreeing to cloud hosting.
• Region chosen, latency measured from your sites.
• Personal data identified and law 09-08 steps anticipated.
• Windows Server and SQL Server licences checked for Azure Hybrid Benefit.
• Second internet link and firewall in place at every site.
• Azure Migrate estimate and pricing calculator, compared with the on-premises option.
• Budget, alerts, backup and an operations owner defined.

How we work

We start with a free initial audit: inventory, usage measurement, feasibility and an estimate of Azure costs against the on-premises option. If Azure is the right fit, we supply the subscription through the Microsoft CSP programme, build secure foundations, migrate in waves and train your teams. After cutover, your Azure resources are monitored 24/7, a critical incident is handled in under 15 minutes, and the monthly report includes consumption and proposed optimisations, as part of our managed IT services in Morocco.

To go further, read our guide to buying Microsoft 365 in Morocco and our Azure and Microsoft 365 in Morocco offering. Then request your free initial audit: we reply within 24 business hours.