Governance policy templates
In brief
The article now explains cross-tenant delegated administration roles, multitenant applications, policy snapshots, default templates, and documented limits.
What Entra admins need to know
Administrators can use the guidance to understand how templates define governance relationships and that template changes don't automatically update existing relationships.
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.
title: Governance policy templates titleSuffix: Microsoft Entra ID Governance description: Learn about governance policy templates and how to use them to enforce consistent governance across tenants in Microsoft Entra ms.topic: concept-article ms.date: 11/11/2026 ai-usage: ai-assisted # Customer intent: As a tenant administrator, I want to understand how governance policy templates define roles and application access so that I can establish consistent governance relationships across tenants.
Governance policy templates
Governance policy templates are a foundational component of the Tenant Governance service, which helps organizations secure Microsoft Entra tenants at scale. Before establishing a governance relationship between tenants, create a governance policy template that defines the relationship behavior. These templates are reusable across distinct governance relationships, enabling consistent and scalable management of cross-tenant access.
How governance policy templates work
A governance policy template serves as a blueprint for governance relationships. When you create a template, you define two key areas of access:
Cross-tenant delegated administration roles - Specify which Microsoft Entra built-in roles users from the governing tenant have in the governed tenant.
Multitenant applications - Select custom applications to create and manage across tenants.
After you create a template, you can use it to establish multiple governance relationships with different governed tenants, ensuring consistent access policies across your organization.
When you create a governance relationship, Tenant Governance captures and stores a policy snapshot with the relationship. This snapshot represents the roles and permissions that applied at the time you established or last updated the relationship.
Updating a governance policy template doesn't automatically update relationships that you created using that template. This design ensures that the governed tenant always has the opportunity to review desired permission changes for the relationship. To apply permission updates to an active relationship, you must repeat the request and approval process.
Relationship lifetime (Preview)
You can optionally set Relationship lifetime to a whole number from 1 to 730 days. The governed tenant reviews the lifetime with the permissions in the governance request. On acceptance, the relationship stores the approved lifetime and calculates its expiration.
An unset lifetime creates a non-expiring relationship. Editing a template doesn't automatically change an active relationship's lifetime. To apply new terms, send a new Initial request using the same template ID and have the governed tenant approve it.
Renewal uses the lifetime and permissions already stored in the relationship's policy snapshot, not a newer version of the template. See Manage relationship expiration and renewal.
Cross-tenant delegated administration configuration
By selecting Microsoft Entra built-in roles and assigning them to a group in the governing tenant, you define which roles (and level of access) users in that group have in the governed tenant. With these roles, users can:
Sign in to the governed tenant using their governing tenant credentials.
Manage the governed tenant without needing a local or business-to-business (B2B) account in that tenant.
Each group can have multiple role assignments, and each policy template can have multiple groups defined. When you create the governance relationship, Tenant Governance creates granular delegated admin privileges (GDAP) role assignments in the governed tenant.
Multitenant application configuration
By selecting custom, multitenant applications in the policy template, you enable centralized application management. When you create the governance relationship, Tenant Governance creates a service principal with the same permissions in the governed tenant.
This capability allows you to manage your custom, multitenant applications at scale from the central governing tenant. You don't need to go into every tenant individually to monitor and maintain least privileged app access.
For example, assume you've built a custom line of business app called Contoso Resource Manager, responsible for monitoring, reporting, and automating resource configuration across your tenants. Use the governance relationship to set up a service principal instance of Contoso Resource Manager across your governed tenants, with the right provisioned permissions consented. When you need to add or remove permissions, do so through the governance relationship instead of making changes and consenting to permissions on a per-tenant basis.
Default policy template
The default policy template is a special template used for secure tenant creation scenarios. When you create a new add-on tenant, Tenant Governance automatically establishes a governance relationship between the parent tenant and the add-on tenant using the default policy template. This setup ensures that new tenants immediately come under centralized tenant administration from the start.
The default policy template has these characteristics:
Unique identifier: Instead of a GUID, the default policy template has an ID of "default."
Configuration required: You must configure the default policy template before you can use it.
Relationships created automatically during add-on tenant creation are excluded from relationship expiration. Setting a lifetime on the default template doesn't by itself schedule expiration for those automatically created relationships.
Limitations
The following limitations apply to governance policy templates:
| Limit | Value |
|---|---|
| Maximum number of multitenant applications per template | 10 |
| Maximum number of permissions per multitenant application | 100 |
| Maximum number of role assignments per template | 10 |
Related content
@@ -1,74 +1,84 @@-----title: Governance policy templates-titleSuffix: Microsoft Entra ID Governance-description: Learn about governance policy templates and how to use them to enforce consistent governance across tenants in Microsoft Entra-ms.topic: concept-article-ms.date: 10/12/2026-ai-usage: ai-assisted-# Customer intent: As a tenant administrator, I want to understand how governance policy templates define roles and application access so that I can establish consistent governance relationships across tenants.------# Governance policy templates--Governance policy templates are a foundational component of the Tenant Governance service, which helps organizations secure Microsoft Entra tenants at scale. Before establishing a governance relationship between tenants, create a governance policy template that defines the relationship behavior. These templates are reusable across distinct governance relationships, enabling consistent and scalable management of cross-tenant access.--> [!NOTE]-> Governance policy templates define cross-tenant access for governance relationships. They aren't [resource policy definitions](resource-policy-concepts.md), which use Rego to evaluate resource changes. Creating a governance policy template doesn't create a resource policy assignment.--## How governance policy templates work--A governance policy template serves as a blueprint for governance relationships. When you create a template, you define two key areas of access:--- Cross-tenant delegated administration roles - Specify which Microsoft Entra built-in roles users from the governing tenant have in the governed tenant.--- Multitenant applications - Select custom applications to create and manage across tenants.--After you create a template, you can use it to establish multiple governance relationships with different governed tenants, ensuring consistent access policies across your organization.--When you create a governance relationship, Tenant Governance captures and stores a policy snapshot with the relationship. This snapshot represents the roles and permissions that applied at the time you established or last updated the relationship.--Updating a governance policy template doesn't automatically update relationships that you created using that template. This design ensures that the governed tenant always has the opportunity to review desired permission changes for the relationship. To apply permission updates to an active relationship, you must repeat the request and approval process.--## Cross-tenant delegated administration configuration--By selecting Microsoft Entra built-in roles and assigning them to a group in the governing tenant, you define which roles (and level of access) users in that group have in the governed tenant. With these roles, users can:--- Sign in to the governed tenant using their governing tenant credentials.--- Manage the governed tenant without needing a local or business-to-business (B2B) account in that tenant.--Each group can have multiple role assignments, and each policy template can have multiple groups defined. When you create the governance relationship, Tenant Governance creates [granular delegated admin privileges (GDAP)](cross-tenant-delegated-administration.md) role assignments in the governed tenant.--## Multitenant application configuration--By selecting custom, multitenant applications in the policy template, you enable centralized application management. When you create the governance relationship, Tenant Governance creates a service principal with the same permissions in the governed tenant.--This capability allows you to manage your custom, multitenant applications at scale from the central governing tenant. You don't need to go into every tenant individually to monitor and maintain least privileged app access.--For example, assume you've built a custom line of business app called Contoso Resource Manager, responsible for monitoring, reporting, and automating resource configuration across your tenants. Use the governance relationship to set up a service principal instance of Contoso Resource Manager across your governed tenants, with the right provisioned permissions consented. When you need to add or remove permissions, do so through the governance relationship instead of making changes and consenting to permissions on a per-tenant basis.--## Default policy template--The default policy template is a special template used for secure tenant creation scenarios. When you create a new add-on tenant, Tenant Governance automatically establishes a governance relationship between the parent tenant and the add-on tenant using the default policy template. This setup ensures that new tenants immediately come under centralized tenant administration from the start.--The default policy template has these characteristics:--- **Unique identifier**: Instead of a GUID, the default policy template has an ID of "default."--- **Configuration required**: You must configure the default policy template before you can use it.--## Limitations--The following limitations apply to governance policy templates:--| Limit | Value |-| --- | --- |-| Maximum number of multitenant applications per template | 10 |-| Maximum number of permissions per multitenant application | 100 |-| Maximum number of role assignments per template | 10 |--## Related content--- [Governance relationships](governance-relationships.md)-- [Set up a governance relationship](how-to-set-up-governance-relationship.md)-- [Cross-tenant delegated administration](cross-tenant-delegated-administration.md)+---
+title: Governance policy templates
+titleSuffix: Microsoft Entra ID Governance
+description: Learn about governance policy templates and how to use them to enforce consistent governance across tenants in Microsoft Entra
+ms.topic: concept-article
+ms.date: 11/11/2026
+ai-usage: ai-assisted
+# Customer intent: As a tenant administrator, I want to understand how governance policy templates define roles and application access so that I can establish consistent governance relationships across tenants.
+---
+
+# Governance policy templates
+
+Governance policy templates are a foundational component of the Tenant Governance service, which helps organizations secure Microsoft Entra tenants at scale. Before establishing a governance relationship between tenants, create a governance policy template that defines the relationship behavior. These templates are reusable across distinct governance relationships, enabling consistent and scalable management of cross-tenant access.
+
+> [!NOTE]
+> Governance policy templates define cross-tenant access for governance relationships. They aren't [resource policy definitions](resource-policy-concepts.md), which use Rego to evaluate resource changes. Creating a governance policy template doesn't create a resource policy assignment.
+
+## How governance policy templates work
+
+A governance policy template serves as a blueprint for governance relationships. When you create a template, you define two key areas of access:
+
+- Cross-tenant delegated administration roles - Specify which Microsoft Entra built-in roles users from the governing tenant have in the governed tenant.
+
+- Multitenant applications - Select custom applications to create and manage across tenants.
+
+After you create a template, you can use it to establish multiple governance relationships with different governed tenants, ensuring consistent access policies across your organization.
+
+When you create a governance relationship, Tenant Governance captures and stores a policy snapshot with the relationship. This snapshot represents the roles and permissions that applied at the time you established or last updated the relationship.
+
+Updating a governance policy template doesn't automatically update relationships that you created using that template. This design ensures that the governed tenant always has the opportunity to review desired permission changes for the relationship. To apply permission updates to an active relationship, you must repeat the request and approval process.
+
+## Relationship lifetime (Preview)
+
+You can optionally set **Relationship lifetime** to a whole number from 1 to 730 days. The governed tenant reviews the lifetime with the permissions in the governance request. On acceptance, the relationship stores the approved lifetime and calculates its expiration.
+
+An unset lifetime creates a non-expiring relationship. Editing a template doesn't automatically change an active relationship's lifetime. To apply new terms, send a new **Initial** request using the same template ID and have the governed tenant approve it.
+
+Renewal uses the lifetime and permissions already stored in the relationship's policy snapshot, not a newer version of the template. See [Manage relationship expiration and renewal](how-to-manage-relationship-expiration.md).
+
+## Cross-tenant delegated administration configuration
+
+By selecting Microsoft Entra built-in roles and assigning them to a group in the governing tenant, you define which roles (and level of access) users in that group have in the governed tenant. With these roles, users can:
+
+- Sign in to the governed tenant using their governing tenant credentials.
+
+- Manage the governed tenant without needing a local or business-to-business (B2B) account in that tenant.
+
+Each group can have multiple role assignments, and each policy template can have multiple groups defined. When you create the governance relationship, Tenant Governance creates [granular delegated admin privileges (GDAP)](cross-tenant-delegated-administration.md) role assignments in the governed tenant.
+
+## Multitenant application configuration
+
+By selecting custom, multitenant applications in the policy template, you enable centralized application management. When you create the governance relationship, Tenant Governance creates a service principal with the same permissions in the governed tenant.
+
+This capability allows you to manage your custom, multitenant applications at scale from the central governing tenant. You don't need to go into every tenant individually to monitor and maintain least privileged app access.
+
+For example, assume you've built a custom line of business app called Contoso Resource Manager, responsible for monitoring, reporting, and automating resource configuration across your tenants. Use the governance relationship to set up a service principal instance of Contoso Resource Manager across your governed tenants, with the right provisioned permissions consented. When you need to add or remove permissions, do so through the governance relationship instead of making changes and consenting to permissions on a per-tenant basis.
+
+## Default policy template
+
+The default policy template is a special template used for secure tenant creation scenarios. When you create a new add-on tenant, Tenant Governance automatically establishes a governance relationship between the parent tenant and the add-on tenant using the default policy template. This setup ensures that new tenants immediately come under centralized tenant administration from the start.
+
+The default policy template has these characteristics:
+
+- **Unique identifier**: Instead of a GUID, the default policy template has an ID of "default."
+
+- **Configuration required**: You must configure the default policy template before you can use it.
+
+Relationships created automatically during add-on tenant creation are excluded from relationship expiration. Setting a lifetime on the default template doesn't by itself schedule expiration for those automatically created relationships.
+
+## Limitations
+
+The following limitations apply to governance policy templates:
+
+| Limit | Value |
+| --- | --- |
+| Maximum number of multitenant applications per template | 10 |
+| Maximum number of permissions per multitenant application | 100 |
+| Maximum number of role assignments per template | 10 |
+
+## Related content
+
+- [Governance relationships](governance-relationships.md)
+- [Set up a governance relationship](how-to-set-up-governance-relationship.md)
+- [Cross-tenant delegated administration](cross-tenant-delegated-administration.md)
