You control B2B guest invitations to specific domains by using external collaboration settings and allow or block lists for invitation domains. This lets you restrict which organisations can be invited or prevent invitations to risky domains. Review the policy regularly, test approved domains before rollout and make sure delegated invitation rights are limited to trusted administrators.
How B2B guest invitation domain controls work in Microsoft Entra ID
The practical control is not just whether guests are allowed, but which invitation destinations are permitted. In Entra ID, that means using external collaboration settings to define the default invitation posture, then layering allow or block lists for domains so your tenant can accept trusted partners while rejecting domains you do not want onboarded.
This is best treated as a policy boundary, not a one-time configuration. The domain list becomes part of your external access governance, so the business question is who may sponsor access, which partner domains are expected, and how quickly the allow or block list can be updated when the partnership landscape changes.
If you are standardising third-party access patterns, the Third-Party, B2B and Contractor Access Guide is the right parent concept for invitation governance, sponsorship and offboarding.
What to check before you rely on an allow or block list
First confirm which collaboration policy is actually in effect for the tenant and whether invitation rights are restricted to the right administrative roles. A domain control can look precise on paper but still be undermined if too many users can invite guests, or if the policy is permissive for high-trust partner flows that were never reviewed.
Then validate the approved domains against real partner identities and mail or tenant naming, not just a spreadsheet. Domain matching mistakes, mergers, rebrands and lookalike domains are common reasons a list becomes stale, so test a few representative invitations before rollout and after any policy change.
For microsoft entra id hardening more broadly, the Active Directory and Entra ID Hardening Guide helps place external collaboration controls alongside other tenant protections.
When allow and block lists reduce risk, and when they do not
Domain filtering reduces exposure to accidental invitations, shadow partnerships and obvious high-risk destinations, but it does not validate the person behind the invitation. A guest from an approved domain can still be the wrong account, and an approved partner tenant can still contain compromised identities or excessive access.
That means domain controls should be paired with invitation scoping, approval workflow and least privilege. If a guest can reach sensitive apps or data once onboarded, the real risk is not the domain itself but the privilege the guest receives after the invitation succeeds.
Where the concern is consent, app access and token abuse rather than guest onboarding alone, Entra ID Applications and Consent Guide is a useful adjacent reference because guest access and app consent are often confused in practice.
Risk and Threat Considerations
Domain allow and block lists reduce unwanted B2B invitations, but they do not stop a trusted or approved domain from being abused after the first invite. The main failure mode is overconfidence: teams assume a clean domain list equals safe external access, then leave invitation rights, guest permissions or partner trust too broad.
Failure mechanism: Attackers or rogue users exploit approved-domain trust, permissive invitation rights or stale partner records to introduce guests that were never intended to be onboarded, then use those accounts to expand access.
Impact: The tenant can accumulate unauthorized guests, unintended collaboration paths and harder-to-trace access to apps, files or directory resources, especially when partner review is infrequent.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Guest invitations create external accounts that must be governed through lifecycle controls. |
| AC-3 — Access Enforcement | Allow and block lists enforce who may be invited from specific domains. | |
| AC-6 — Least Privilege | Delegated invitation rights should be limited to trusted administrators with minimal privilege. | |
| Recommendation — Restrict guest account creation, review external accounts regularly, and remove stale invitations or access. Enforce domain-based invitation policy so only approved external organisations can be onboarded. Limit invitation authority to the smallest trusted admin set and remove broad invite permissions. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | External collaboration policies are access-control decisions over who may be invited and admitted. |
| Recommendation — Define and enforce external invitation rules as part of the organisation's access-control policy. | ||
Practitioner Guidance
What to verify: Check both the invitation domain list and the delegation model. A sound configuration should answer two questions clearly: which domains are permitted, and which administrators or workflows can create invitations.
Decision rule: If the domain is approved but the business owner cannot explain why that partner needs access, block the invitation anyway until the sponsor and use case are documented. If the domain is blocked, do not create one-off exceptions without a reviewable approval trail.
What good looks like: The approved list is small, current and tied to named partner relationships, while guest invitations are limited to trusted admins or controlled workflows and reviewed on a predictable cadence.
Practitioner takeaway: Treat domain controls as a front-door filter, not a complete trust decision; the real security outcome depends on who can invite, what guests can reach after they arrive, and how quickly stale partner trust is removed.
Related resources from NHI Mgmt Group
- How do you investigate AI agent sign-ins in Microsoft Entra Agent ID?
- How do you secure a Model Context Protocol (MCP) server with Microsoft Entra ID?
- How do you secure third-party AI agents such as Amazon Bedrock with Microsoft Entra Agent ID?
- How do you apply least privilege to application permissions in Microsoft Entra ID?