Cross-tenant access settings and user-friendly Access Reviews simplify the management of guest accounts in Azure Active Directory.
Efficient collaboration while maintaining security standards is often difficult, especially when it comes to the end-user experience. Business-to-business (B2B) transactions are made in the cloud, but the cloud itself is a dangerous place. Passwords should not be accepted as the only credential, and multifactor authentication (MFA) should be the standard. In this context, it is less than useful that the MFA status is – thus far – only valid within the boundaries of the tenant and that other tenants are not trusted. If two communication partners are committed to a modern work approach with zero trust, things become even more difficult: The device status cannot be transferred either.
New Possibilities with xTAS
Cross-tenant access settings (xTAS) offer an opportunity to improve this situation. The feature is designed to control collaboration fully across tenant boundaries and let organizations control inbound and outbound collaboration by defining tenant-wide and partner-specific rules (Figure 1).
Figure 1: The default settings for cross-tenant access for B2B collaboration give you free rein. If so desired, you can establish more granular
...
Use Express-Checkout link below to read the full article (PDF).
Azure Active Directory Identity Governance brings security processes to organizations with users who access resources or collaborate with partners in the cloud.
Configuration and security of authorization assignment and access control by Entra ID, formerly Azure Active Directory, requires careful consideration. We reveal how configuration as code works with PowerShell and Microsoft 365 DSC for tenant configuration in Entra ID.
The declarative PowerShell Desired State Configuration extension supports easy and transparent configuration of systems and applications. We describe the fairly complex initial setup and use of the Microsoft 365 Desired State Configuration.