Microsoft Entra ID Governance
Governance

Licensing

In brief

The licensing documentation now explains that most preview resource policy operations require an Entra ID Governance service plan; P1 or P2 alone is insufficient. It also documents operation exceptions, continuing role/API requirements, and `doNotEnforce` assignment behavior.

What Entra admins need to know

Administrators should verify licensing and understand that `doNotEnforce` assignments still evaluate requests; no mandatory action is stated.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

For more information about the general tenant creation requirements, see Create a new tenant in Microsoft Entra ID.

Resource policy (preview)

Most resource policy operations during preview require a Microsoft Entra ID Governance service plan, available with Microsoft Entra ID Governance or an offering such as Microsoft Entra Suite. Microsoft Entra P1 or P2 alone doesn't meet this requirement.

The features-by-license tables list required operations and exceptions for built-in and custom policies. Role and API permission requirements still apply to operations that don't require this service plan.

An enabled assignment in doNotEnforce mode still evaluates requests. Creating or editing that assignment requires the service plan; switching to doNotEnforce isn't the same as deactivating it.

For feature behavior and availability, see What is Microsoft Entra resource policy?. To assign a built-in policy, see the built-in policy quickstart.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…