Cross-Tenant Access Settings for Secure Collaboration with Government Delivery Partners

Cross-Tenant Access Settings for Secure Collaboration with Government Delivery Partners

Western Australian government agencies rarely deliver major programmes alone. Shared service arrangements, contracted delivery partners, and inter-agency projects routinely require staff from separate Microsoft Entra tenants to work on common documents, applications, and Teams channels. Business-to-business (B2B) collaboration in Microsoft Entra ID makes this possible, yet every external identity invited into a tenant represents a new path that an attacker could attempt to exploit. The challenge for agencies is to enable genuine partner collaboration while ensuring that each new connection is deliberate, scoped, and governed rather than open by default.

Cross-tenant access settings give administrators granular control over how external identities from other Entra tenants are treated on both the inbound and outbound paths. Rather than accepting whatever the invited user's home tenant asserts, an agency can decide which partner organisations it trusts, which users and groups may collaborate, and which applications they may reach. Configured well, these settings allow collaboration to proceed without quietly widening the attack surface. Configured poorly or left at permissive defaults, they can grant far broader access than any project requires.

Understanding the cross-tenant access model

Cross-tenant access settings sit within Microsoft Entra External ID and apply to collaboration between Entra tenants specifically, which is the common case for one WA Government agency working with another or with a corporate delivery partner that also runs Microsoft 365. The model separates default settings, which apply to every external tenant you have not explicitly configured, from organisation-specific settings, which you create for named partners. This separation matters because it lets an agency keep a restrictive baseline for the wider world while opening targeted, well-understood access for the partners it actually works with. The default posture should therefore be conservative, with trust extended only where a business relationship justifies it.

Within each configuration you control inbound access, which governs how external users enter your tenant, and outbound access, which governs how your own users collaborate in partner tenants. For each direction you can scope B2B collaboration to specific users, groups, and applications, so a partner's project team can be granted access to one site or application rather than to the tenant as a whole. Understanding this inbound and outbound distinction is essential, because an overly generous outbound setting can expose your users to partner environments whose security controls you do not manage. Treating each direction as a separate decision helps agencies apply the principle of least privilege consistently.

Configuring inbound trust without weakening controls

Inbound trust settings determine whether your tenant will accept security claims that a guest user's home tenant has already satisfied. You can choose to trust multifactor authentication completed in the home tenant, as well as claims that the user's device is compliant or is hybrid Entra joined. Trusting these claims improves the experience for legitimate collaborators because they are not challenged twice, but it also means you are relying on the partner tenant to enforce those controls correctly. For this reason, trust settings should be enabled only for named partner organisations whose security practices you have assessed, never as a blanket default for all external tenants.

When combined with Conditional Access, inbound settings become a powerful way to enforce agency requirements regardless of what the partner tenant does. A Conditional Access policy can require multifactor authentication and a compliant device for guest and external users, and the trust settings determine whether a home-tenant assertion satisfies that requirement or whether the user must re-authenticate in your tenant. Agencies handling sensitive information may prefer not to trust external multifactor authentication and instead require it to be performed against their own tenant, accepting a small amount of user friction in exchange for assurance. Documenting why each trust decision was made, and reviewing it when the partner relationship changes, keeps the configuration defensible during audit.

Governance, monitoring, and alignment with Australian guidance

Technical configuration is only part of secure collaboration; the surrounding governance determines whether controls stay effective over time. Access reviews in Microsoft Entra ID allow agencies to periodically confirm that guest accounts still correspond to active engagements and to remove those that do not, which prevents the slow accumulation of dormant external identities. Sign-in logs and the dedicated cross-tenant access activity reporting help administrators see which partner tenants users are actually collaborating with, so permissive settings can be identified and tightened. These reviews should be scheduled rather than ad hoc, with clear ownership assigned so that no partner connection outlives its purpose.

Cross-tenant access decisions should also align with broader Australian government expectations for identity and access management. The Australian Cyber Security Centre's Essential Eight and the Information Security Manual both emphasise strong multifactor authentication, least privilege, and restricting administrative and external access, all of which map directly onto inbound trust and application scoping choices. Agencies should record their cross-tenant posture in the same risk and governance frameworks they use for internal identity controls, so external collaboration is assessed with the same rigour as any other access pathway. Pairing careful configuration with disciplined review gives WA Government agencies a practical way to collaborate with delivery partners while keeping the attack surface deliberate and well understood.

References

Coffee's on us!

Our 💟 for great ☕is second only to our dedication to delivering strategies that drive your business forward.

Let’s discuss how our solutions can fuel your success.
Image
Novata Solutions

Smart and effective
solutions for businesses.

Follow Us - Fb. / X. / Li. / yT.

© Novata Solutions

Head Office

Level 7, 12 St Georges Tce
Perth WA 6000

Contact Info

[email protected]
Ph 1300 NOVATA

Image

ISO 27001

Image

ISO 9001

Image

SMB 1001 Gold

Image

In the spirit of reconciliation Novata Solutions acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their Elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today. This land always was, and always will be Aboriginal Land.

Image

Novata Solutions is committed to embracing diversity and eliminating all forms of discrimination through education. We welcomes all people and is respectful of individual identities.