Managed WordPress hosting for sites running on Azure App Service.
App Service is a deployment target rather than a server. Your configuration is in the portal, your uploads are on a mount, and there is no box to take a copy of.
Where an App Service site actually keeps things.
Everything that would normally be in a file on a server is somewhere else, which is exactly what makes the export unusual.
Configuration in App Settings
Database credentials, salts and feature flags are injected as environment variables from the portal. wp-config.php reads them, so the file itself contains none of the values you need.
A flexible server holding the data
Azure Database for MySQL runs separately with its own firewall rules and enforced TLS, so the export is taken there rather than from the app.
Uploads on mounted storage
Media commonly sits on an Azure Files share mounted into the app, because the app's own filesystem is not somewhere to keep anything you want to survive a restart.
A deployment slot doing staging
Slots are how App Service does staging, and a slot has its own settings. Which slot is actually serving production gets confirmed before anything is copied.
Front Door in front of everything
Caching, WAF rules and custom routing are frequently configured in Azure Front Door or CDN, which sees traffic long before WordPress does.
Read the portal, then take the copy.
An App Service export that starts with the filesystem gets a site that cannot connect to its own database, because none of the credentials are in the files.
- App Settings exported before anything else
- MySQL flexible server dumped with TLS enforced
- Mounted file share collected
- Slots and Front Door rules confirmed
No cold starts, no scaling rules to write.
App Service scales when you configure it to. The difference here is that the tuning is already done and there is no plan tier deciding whether PHP has enough memory.
What we change when a site arrives from Azure
The theme here is that App Service deliberately keeps state out of the application, so the migration has to go and find it.
| Setting | What we do | Why |
|---|---|---|
| Configuration values | App Settings read from the portal and written into real configuration | App Service injects credentials and salts as environment variables, so wp-config.php on disk holds only references and a filesystem copy produces a site that cannot reach its own database. |
| Database | Exported from Azure Database for MySQL with its TLS requirement honoured | The flexible server sits behind its own firewall and refuses unencrypted connections, so an export attempted the usual way is rejected before it starts. |
| Uploads | Collected from the mounted Azure Files share | App Service treats the application filesystem as disposable, so media is kept on a mounted share that a deployment package or a slot swap never contains. |
| Deployment slots | Production slot confirmed before the export is taken | Staging on App Service is a slot with its own settings, and copying the wrong one produces a migration of a site nobody was visiting. |
| Front Door rules | Caching, WAF and routing behaviour recreated at our edge | Front Door handles those requests before App Service is involved, so the rules are invisible to WordPress and vanish silently when the endpoint is decommissioned. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
My wp-config.php has no database credentials in it. Is that normal?
How do you export Azure Database for MySQL?
Where are my uploaded images?
I use deployment slots. Which one do you migrate?
What replaces Front Door?
Stop deploying WordPress like an application.
Free migration, configuration recovered from the portal, and storage brought back with it.