Guest lifecycle policies in Lifecycle Workflows
In brief
The preview designation was removed. The documentation now describes rule-specific remediation grace periods, fallback notification recipients, guest posture insights, blocked-action reporting, and policy version history.
What Entra admins need to know
No action is required. Administrators can use the documented controls and reporting to manage guest lifecycle enforcement more precisely.
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.
Guest lifecycle policies in Lifecycle Workflows (preview)
Guest lifecycle policies in Lifecycle Workflows help you govern external collaboration at scale. You can define which Microsoft Entra guest users are covered, configure rules that evaluate guest lifecycle signals, notify sponsors or guests, and automatically disable or delete accounts that no longer meet policy requirements.
- Policies apply to users whose Microsoft Entra
userTypeproperty is set toGuest, regardless of how the guest account was created or invited. - Creation-date scope uses the guest object's
createdDateTimeproperty and can include guests created through first-party applications or other invitation sources. - Attribute-based rules can use supported standard user properties, on-premises extension attributes 1 through 15, directory extensions, and custom security attributes, subject to the attributes exposed in the preview experience.
- Group inclusion and exclusion use direct membership. Nested groups aren't evaluated.
- Access-based conditions depend on access package assignment data.
- Browse to ID Governance > Lifecycle Workflows > Lifecycle Policies > Guest Lifecycle Policies > Create policy.
- Enter a unique policy name and a description that identifies the intended guest population and purpose.
- Configure the policy scope and rules.
- Choose the policy action and, if desired, the grace period.
- Review the notification behavior.
- Set the policy priority if other guest lifecycle policies exist.
- Review the configuration, create the policy, and enable it when you're ready for evaluation and enforcement.
Configure policy rules
A policy can contain multiple rules. A rule determines whether a guest remains compliant or becomes eligible for enforcement. Confirm the final rule-combination behavior in a test environment before you enable the policy in production.
| Policy rule | Default | Configuration range | Purpose |
|---|
- Delete: Delete the guest account.
- Disable: Disable the guest account.
- Disable, then delete: Immediately disable the account, and then automatically delete it after a grace period from 7 through 90 days. The default is 30 days.
- Grace period: If a guest becomes noncompliant with any policy rule, delay the policy action by configuring a grace period of at least one day. The default is seven days.
Notifications
- Disable notification: Lifecycle Workflows immediately notifies the sponsor when the guest account is disabled and access is revoked.
- Delete notification: Lifecycle Workflows immediately notifies the sponsor when the guest account is deleted and access is revoked.
Multiple policies and precedence
You can configure multiple guest lifecycle policies with different scopes and settings. You can view, enable, disable, delete, and reorder policies. When more than one policy matches a guest, the configured priority determines which policy is enforced.
Monitor and manage policies
View policy processing and scope
For each policy, you can view:
- Each guest's compliance state, such as Compliant, Noncompliant, or Not evaluated.
- The policy being enforced for a selected guest.
Delete and restore a policy
Deleted policies are soft-deleted and can be restored. A restored policy is disabled regardless of its previous state and is placed at the lowest priority. Review its scope, rules, notifications, action, and precedence before you enable it again.
- Scope evaluation: Lifecycle Workflows identifies guest users who match the policy's inclusion rules and don't match its exclusions.
- Condition evaluation: Lifecycle Workflows evaluates the policy rules for each guest to determine whether the guest is compliant or noncompliant.
- Enforcement: If the guest is noncompliant, Lifecycle Workflows performs the configured action. If a grace period is enabled, enforcement occurs when the grace period ends.
- Notification: Lifecycle Workflows sends the applicable notifications to the sponsor and guest.
- Status update: Lifecycle Workflows updates policy processing and guest compliance information in the management experience.
Guest lifecycle policies in Lifecycle Workflows help you govern external collaboration at scale. You can define which Microsoft Entra guest users are covered, configure rules that evaluate guest lifecycle signals, notify sponsors or guests, and automatically disable or delete accounts that no longer meet policy requirements.
- Policies apply to users whose Microsoft Entra
userTypeproperty is set toGuest, regardless of how the guest account was created or invited. - Creation-date scope uses the guest object's
createdDateTimeproperty and can include guests created through first-party applications or other invitation sources. - Attribute-based rules can use supported standard user properties, on-premises extension attributes 1 through 15, directory extensions, and custom security attributes supported by guest lifecycle policies.
- Group inclusion and exclusion use direct membership. Nested groups aren't evaluated.
- Access-based conditions depend on access package assignment data.
- Browse to ID Governance > Lifecycle Workflows > Lifecycle Policies > Guest Lifecycle Policies > Create policy.
- Enter a unique policy name and a description that identifies the intended guest population and purpose.
- Configure the policy scope and rules.
- Choose the policy action and configure remediation grace periods for applicable rules.
- Review the notification behavior.
- Set the policy priority if other guest lifecycle policies exist.
- Review the configuration, create the policy, and enable it when you're ready for evaluation and enforcement.
Configure policy rules
A policy can contain multiple rules. A rule determines whether a guest remains compliant or becomes eligible for enforcement. You can configure a separate remediation grace period for each lifecycle rule. This gives guests or sponsors time to resolve a specific issue without delaying enforcement of another rule whose grace period has expired. Confirm the rule-combination behavior in a test environment before you enable the policy in production.
| Policy rule | Default | Configuration range | Purpose |
|---|
- Delete: Delete the guest account.
- Disable: Disable the guest account.
- Disable, then delete: Immediately disable the account, and then automatically delete it after a grace period from 7 through 90 days. The default is 30 days.
- Rule-specific remediation grace periods: Configure a separate grace period for each lifecycle rule. A grace period for one rule doesn't delay enforcement of another rule whose grace period has expired.
Notifications
- Disable notification: Lifecycle Workflows immediately notifies the sponsor when the guest account is disabled and access is revoked.
- Delete notification: Lifecycle Workflows immediately notifies the sponsor when the guest account is deleted and access is revoked.
You can configure a fallback recipient to receive notifications when Lifecycle Workflows can't resolve the intended recipient.
Multiple policies and precedence
You can configure multiple guest lifecycle policies with different scopes and settings. You can view, enable, disable, delete, and reorder policies. When more than one policy matches a guest, the configured priority determines which policy is enforced.
Monitor and manage policies
Review guest posture insights
The Lifecycle Workflows overview page shows counts of guests who aren't under a policy, guests without sponsors, and guests with unredeemed invitations. Use these insights to assess your guest population and identify opportunities to apply lifecycle governance.
View policy processing and scope
For each policy, you can view:
- Each guest's compliance state, such as Compliant, Noncompliant, or Not evaluated.
- The policy being enforced for a selected guest.
Review privileged guests and blocked actions
Policy reporting identifies guests whose role assignments or membership in a restricted administrative unit prevent automatic disablement or deletion. Any Microsoft Entra role assignment prevents Lifecycle Workflows from performing lifecycle actions on a guest. Review the report to identify blocked actions and resolve the role assignment or restricted administrative unit membership.
View policy version history
On the policy's Policy Overview page, view previous versions to understand how the policy configuration changed over time.
Delete and restore a policy
Deleted policies are soft-deleted and can be restored. A restored policy is disabled regardless of its previous state and is placed at the lowest priority. Review its scope, rules, notifications, action, and precedence before you enable it again.
- Scope evaluation: Lifecycle Workflows identifies guest users who match the policy's inclusion rules and don't match its exclusions.
- Condition evaluation: Lifecycle Workflows evaluates the policy rules for each guest to determine whether the guest is compliant or noncompliant.
- Enforcement: If the guest is noncompliant, Lifecycle Workflows performs the configured action when the grace period for that rule ends.
- Notification: Lifecycle Workflows sends the applicable notifications to the sponsor and guest.
- Status update: Lifecycle Workflows updates policy processing and guest compliance information in the management experience.
@@ -3,15 +3,12 @@ title: Guest lifecycle policies in Lifecycle Workflows description: Learn how to configure guest lifecycle policies in Lifecycle Workflows to govern external collaboration. ms.subservice: lifecycle-workflows ms.topic: how-to-ms.date: 03/13/2026+ms.date: 11/13/2026 ai-usage: ai-assisted #Customer Intent: As an identity governance administrator, I want to configure guest lifecycle policies so that I can govern external collaboration at scale. --- -# Guest lifecycle policies in Lifecycle Workflows (preview)--> [!IMPORTANT]-> Guest lifecycle policies are currently in preview. Preview features are provided without a service-level agreement and aren't recommended for production workloads. Certain features might not be supported or might have limited capabilities. This preview is available in the public cloud.+# Guest lifecycle policies in Lifecycle Workflows Guest lifecycle policies in Lifecycle Workflows help you govern external collaboration at scale. You can define which Microsoft Entra guest users are covered, configure rules that evaluate guest lifecycle signals, notify sponsors or guests, and automatically disable or delete accounts that no longer meet policy requirements. @@ -50,7 +47,7 @@ You need one of the following roles to manage guest lifecycle policies: - Policies apply to users whose Microsoft Entra `userType` property is set to `Guest`, regardless of how the guest account was created or invited. - Creation-date scope uses the guest object's `createdDateTime` property and can include guests created through first-party applications or other invitation sources.-- Attribute-based rules can use supported standard user properties, on-premises extension attributes 1 through 15, directory extensions, and custom security attributes, subject to the attributes exposed in the preview experience.+- Attribute-based rules can use supported standard user properties, on-premises extension attributes 1 through 15, directory extensions, and custom security attributes supported by guest lifecycle policies. - Group inclusion and exclusion use direct membership. Nested groups aren't evaluated. - Access-based conditions depend on access package assignment data. @@ -72,7 +69,7 @@ The following procedure explains how to create a guest lifecycle policy, define 1. Browse to **ID Governance** > **Lifecycle Workflows** > **Lifecycle Policies** > **Guest Lifecycle Policies** > **Create policy**. 1. Enter a unique policy name and a description that identifies the intended guest population and purpose. 1. Configure the policy scope and rules.-1. Choose the policy action and, if desired, the grace period.+1. Choose the policy action and configure remediation grace periods for applicable rules. 1. Review the notification behavior. 1. Set the policy priority if other guest lifecycle policies exist. 1. Review the configuration, create the policy, and enable it when you're ready for evaluation and enforcement.@@ -95,7 +92,7 @@ Scoping options include: ## Configure policy rules -A policy can contain multiple rules. A rule determines whether a guest remains compliant or becomes eligible for enforcement. Confirm the final rule-combination behavior in a test environment before you enable the policy in production.+A policy can contain multiple rules. A rule determines whether a guest remains compliant or becomes eligible for enforcement. You can configure a separate remediation grace period for each lifecycle rule. This gives guests or sponsors time to resolve a specific issue without delaying enforcement of another rule whose grace period has expired. Confirm the rule-combination behavior in a test environment before you enable the policy in production. | Policy rule | Default | Configuration range | Purpose | | --- | --- | --- | --- |@@ -114,7 +111,7 @@ Choose the action to take when a guest doesn't satisfy the policy by the enforce - **Delete:** Delete the guest account. - **Disable:** Disable the guest account. - **Disable, then delete:** Immediately disable the account, and then automatically delete it after a grace period from 7 through 90 days. The default is 30 days.-- **Grace period:** If a guest becomes noncompliant with any policy rule, delay the policy action by configuring a grace period of at least one day. The default is seven days.+- **Rule-specific remediation grace periods:** Configure a separate grace period for each lifecycle rule. A grace period for one rule doesn't delay enforcement of another rule whose grace period has expired. ### Notifications @@ -124,6 +121,8 @@ Lifecycle Workflows can send up to three notifications during enforcement. The n - **Disable notification:** Lifecycle Workflows immediately notifies the sponsor when the guest account is disabled and access is revoked. - **Delete notification:** Lifecycle Workflows immediately notifies the sponsor when the guest account is deleted and access is revoked. +You can configure a fallback recipient to receive notifications when Lifecycle Workflows can't resolve the intended recipient.+ ### Multiple policies and precedence You can configure multiple guest lifecycle policies with different scopes and settings. You can view, enable, disable, delete, and reorder policies. When more than one policy matches a guest, the configured priority determines which policy is enforced.@@ -137,6 +136,10 @@ A tenant can have up to 20 guest lifecycle policies. ## Monitor and manage policies +### Review guest posture insights++The Lifecycle Workflows overview page shows counts of guests who aren't under a policy, guests without sponsors, and guests with unredeemed invitations. Use these insights to assess your guest population and identify opportunities to apply lifecycle governance.+ ### View policy processing and scope For each policy, you can view:@@ -146,6 +149,14 @@ For each policy, you can view: - Each guest's compliance state, such as **Compliant**, **Noncompliant**, or **Not evaluated**. - The policy being enforced for a selected guest. +### Review privileged guests and blocked actions++Policy reporting identifies guests whose role assignments or membership in a restricted administrative unit prevent automatic disablement or deletion. Any Microsoft Entra role assignment prevents Lifecycle Workflows from performing lifecycle actions on a guest. Review the report to identify blocked actions and resolve the role assignment or restricted administrative unit membership.++### View policy version history++On the policy's **Policy Overview** page, view previous versions to understand how the policy configuration changed over time.+ ### Delete and restore a policy Deleted policies are soft-deleted and can be restored. A restored policy is disabled regardless of its previous state and is placed at the lowest priority. Review its scope, rules, notifications, action, and precedence before you enable it again.@@ -154,7 +165,7 @@ Deleted policies are soft-deleted and can be restored. A restored policy is disa 1. **Scope evaluation:** Lifecycle Workflows identifies guest users who match the policy's inclusion rules and don't match its exclusions. 1. **Condition evaluation:** Lifecycle Workflows evaluates the policy rules for each guest to determine whether the guest is compliant or noncompliant.-1. **Enforcement:** If the guest is noncompliant, Lifecycle Workflows performs the configured action. If a grace period is enabled, enforcement occurs when the grace period ends.+1. **Enforcement:** If the guest is noncompliant, Lifecycle Workflows performs the configured action when the grace period for that rule ends. 1. **Notification:** Lifecycle Workflows sends the applicable notifications to the sponsor and guest. 1. **Status update:** Lifecycle Workflows updates policy processing and guest compliance information in the management experience. 