An Azure managed PostgreSQL database service for app development and deployment.
I don't think this can be cleared while the server stays on Burstable. It looks like the disable call hits the same SKU check that blocks enabling mirroring, so it fails before the setting is turned off. The cleanest self-service route is a short, temporary scale-up:
- Pick a quiet window. A compute scale restarts the server, usually for a minute or two, but your data and credentials aren't touched.
- In the portal, go to Settings > Compute + storage and move to a small General Purpose size (for example Standard_D2ds_v5).
- Once the server is back to Ready, stop mirroring again (
az postgres flexible-server fabric-mirroring stopor the portal) and confirmazure.fabric_mirror_enabledshowsoff. - Scale back down to Standard_B1ms.
- Go ahead with enabling Microsoft Entra authentication.
Compute is billed hourly, so keeping the General Purpose window short keeps the extra cost small. If you'd rather not touch the tier at all, a backend reset by the PostgreSQL product team is the only other option.
Would a short restart window work for this server?
If my response resolved your issue, please consider accepting it as the answer. If the issue persists, let me know and I'll be happy to continue helping.
Reference: