I have two companies, A and B, operating under different Microsoft tenants. Company A hosts a virtual server in Azure to which they connect via VPN. Now, Company B needs several of their employees to access this server. While I could create user accounts in Company A that mirror what Company B already has, I'm looking for a more sophisticated and budget-friendly solution. Apparently, Microsoft has put the brakes on cross-tenant access, but I'm curious if there are still viable options available. Any advice would be appreciated!
3 Answers
Just a heads up, Azure itself doesn’t manage users specific to any tenant. Each tenant is independent. But from an authentication perspective, it’s crucial because it determines how users will access different resources. Keeping that in mind should help you figure things out.
For network access, consider using a Standard Load Balancer in front of the VM in Company A and set up Private Link Service. This allows you to manage DNS and private endpoints in Company B. If the VM relies on local accounts, you'll just create logins for Company B's users. If you're using Active Directory or Entra ID, it's easier to set up accounts for Company B users in Tenant A. It's a minor hassle for them but keeps things simple on your end! Guest accounts might be a good option too.
The simplest way to handle this is by creating guest users. You can add users from Company B as guests in Company A's tenant. It might feel a bit clunky since they would need separate logins, but at least you won’t have to manage overlapping credentials. If you're looking for something a bit fancier, consider setting up cross-tenant B2B collaboration in Microsoft Entra. Check out Microsoft’s docs for more on that.
Yeah, authentication can really change the game, especially when making sure everything runs smoothly across those tenants!