Identity governance
When the project ends, what happens to guest access?
Guest-access automation needs business ownership, careful scope and a safe way to handle mistakes.
Analysis of Microsoft's November 2026 update. The product feature discussed is a public preview, not a production recommendation.
The invitation is only the beginning
A supplier joins a project, a consultant receives access, or a partner starts collaborating. The invitation has a clear purpose. The harder question comes later: who confirms that access is still needed?
Microsoft's 6 November 2026 Entra roundup highlights guest lifecycle policies as a public preview. The accompanying documentation describes rules based on signals such as sponsor attestation, activity and invitation redemption, with configurable account disablement or deletion. This is a product development worth evaluating, not a reason to switch on automatic deletion across a live directory. [1] [2]
Microsoft explicitly says the preview is available in the public cloud, has no service-level agreement and is not recommended for production workloads. Those limits belong in the decision, not in the small print. [2]
Start with the access decision
Recent activity and business need are different questions. A guest might sign in regularly even though their engagement has ended. Another might legitimately need occasional access but remain inactive between milestones.
Vula Connect's recommended starting point is a short ownership record: the business purpose, the responsible sponsor, the resources involved, a review point and the person authorised to approve removal. These are practical governance recommendations, not a new technical standard or a claim about a universal legal deadline.
Automation can apply a rule consistently. It cannot decide whether the rule represents your business relationship.
Scope is a safety control
The current Microsoft documentation applies these policies to objects whose userType is Guest. That is a directory property, not a guarantee that every external collaborator in every application is covered. Group scoping uses direct membership; nested groups are not evaluated. [2]
Overlapping policies also deserve attention. Microsoft documents that only the highest-precedence matching policy applies to a guest; lower-priority policies are not evaluated for that guest. An exclusion from one policy therefore should not be treated as protection from every other policy. [2]
Before any approved evaluation, map the intended population and exclusions. Include a case that matches two policies, a guest without a usable sponsor contact and a guest in a nested group. The aim is to expose assumptions before they become access failures.
Disablement and deletion are not interchangeable
The preview supports disablement, deletion, or disablement followed by deletion after a grace period. Microsoft documents evaluation once per day, rather than an instant response to every change. [2]
Treat this as lifecycle governance, not as an emergency containment guarantee. An active incident still needs the organisation's established response process.
For a controlled test, use synthetic guest accounts in an approved nonproduction environment. Decide in advance how to detect an incorrect action, stop further enforcement and recover the affected test access. Check the actual application experience rather than assuming that a successful directory action proves every downstream session or entitlement has ended.
Check costs before enabling a trial
Microsoft's documentation requires an Entra ID Governance licence and an Azure subscription connected to the guest add-on meter. Its licensing guidance lists guest lifecycle policy disablement, deletion and sponsor attestation among billable governance actions under the guest monthly-active-user model. [2] [3]
Do not assume that "public preview" means "free". Have the billing owner review the current terms and approve any evaluation that could incur charges.
A useful first outcome
The first deliverable need not be an enabled policy. A worthwhile outcome is an agreed guest-access lifecycle: named sponsors, explicit review rules, understood exceptions, a recovery approach and a documented cost decision.
If a nonproduction evaluation is authorised, record what the policy actually did, which notifications arrived and where the observed behaviour differed from expectations. Keep real guest information out of public reports and restrict access to any evaluation evidence.
The goal is accountable external access, not the largest possible deletion count.
Sources and scope
Primary sources checked on . Product status and licensing may change.
- Microsoft Entra: What's new in November 2026
Published and updated 6 November 2026; a roundup of the preceding month's developments. Labels guest lifecycle policies Public Preview, not general availability. - Microsoft Learn: Guest lifecycle policies in Lifecycle Workflows
Living documentation checked 16 November 2026. Covers preview limitations, licensing, guest scope, direct membership, policy precedence, enforcement, notifications and daily evaluation. Documentation metadata is not treated as a feature-launch date. - Microsoft Learn: Microsoft Entra ID Governance licensing for guest users
Living documentation checked 16 November 2026. Supports the MAU billing discussion; no price or universal free allowance is asserted.
Scope matters. This is source-based analysis, not tenant-tested implementation advice. No tenant was accessed, feature enabled, guest contacted or paid service started for this article. Recheck preview status, licensing and documentation before implementation. Microsoft product references do not imply a Vula partnership, certification or endorsement.