Azure Event Grid System Topic Deployment Fails with Maintenance Configuration Source — Anyone Else Experiencing This?

Jeroen Monnens 20 Reputation points
2025-08-27T12:20:54.3566667+00:00

Hi all,

I'm running into a consistent issue when trying to deploy an Event Grid System Topic using a Maintenance Configuration as the source in Azure. The deployment fails with the following error:

Creation of System Topic has failed with error: Unable to verify access to resource /subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Maintenance/MaintenanceConfigurations/<MaintenanceConfigurationName>. Please try again in a few minutes. Event Subscription will not be created.

What I've tried:

  • Deployment via Azure Portal
  • Deployment using Bicep
  • Deployment using the EventGrid PowerShell module
  • Tested across multiple subscriptions and different tenants

The error is consistent across all methods and environments. Permissions and role assignments appear to be correctly configured, and the Maintenance Configuration resource is valid and accessible. No special characters in the name either.

My question:

  • Has anyone successfully deployed a System Topic with a Maintenance Configuration as the source in the last weeks?
  • Is there a known issue? We have deployed these in the past without any issues.
  • Could this be a broader issue on Azure’s side?

Any insights, workarounds, or confirmation from others experiencing the same would be super helpful.

Thanks in advance!

Azure Event Grid
Azure Event Grid
An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
{count} votes

1 answer

Sort by: Most helpful
  1. Jeroen Monnens 20 Reputation points
    2025-09-15T13:05:50.77+00:00

    Microsoft Support:

    We’ve received an update from our Product Group team regarding the issue you reported. After thorough investigation, they have identified a limitation within Event Grid. Currently, creating system topics in Azure subscriptions managed from a separate tenant via Azure Lighthouse is not supported.

    This functionality was previously working; however, earlier this year, we migrated to a new system for checking user permissions during system topic creation. Unfortunately, this change introduced limitations specifically affecting Azure Lighthouse scenarios.

    To resolve this, a code change is required, which will enable proper support for this scenario. The team has informed us that implementation and deployment will take a minimum of several weeks, and at this time, they do not have a concrete ETA.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.