User Profile
Brad13
Copper Contributor
Joined 9 years ago
User Widgets
Recent Discussions
Re: Azure AD Connect - One forest - Two tenants - Same OUs
LainRobertson josequintino Thank you both for the very helpful information. Lain, in our scenario we would be synchronized to two production tenants contosoA.com and contosoB.com. In this scenario if the user object has UPN, mail, proxyAddresses, sip Address that reflects one of the two wouldn't there be a need to do some custom attribute mapping in the on prem AD to ensure the respective domain values are correct for the tenant being synchronized to? Meaning UPN reflecting @contosoA.com but being synchronized to @contosoB.com would need a custom attribute mapping that contains the correct @contosoB.com address?1KViews0likes1CommentRe: Azure AD Connect - One forest - Two tenants - Same OUs
LainRobertson Thank you for the response, we definitely know there will be a lot of challenges with this. Here's the interesting part, the tenant has the users provisioned already through powershell directly into the tenant. We are being asked to bolt on a new Azure AD Connect, the immutable IDs match what is in the on premise AD. Would we need custom attribute mappings for upn, proxy address, mail, and sip if the same user object is going to be synchronized from on premise AD with the different domains to two tenants? We have been pushing to create two IDs since the two tenants are really separate entities. B2B can be used down the road for cross tenant collaboration.970Views0likes1CommentRe: Single Forest AD Sync to Multiple Azure AD
Max Fritz Will any users need to exist in both tenants? That's where things can get sticky. Microsoft has come a long way in this regards, but we are about to face this exact situation and I see no clear answer as to having two Azure AD Connect syncs look at the same OUs in the same forest. With the potential for the same user object to exist in both tenants with different domains. Is this possible today?391Views0likes0CommentsAzure AD Connect - One forest - Two tenants - Same OUs
Hi All, We are looking to add a second Azure AD Connect to our environment to have users synchronized to a new tenant(second tenant different domain). According to Microsoft this is a supported approach, but is it also ok to have the same OUs as part of both syncs? We currently have situations where the same user object may belong to ContosoA and ContosoB or would the users that belong to each tenant need to be part of their own OUs and exclusive to each? Thanks.Exchange On Premise with OAuth to Microsoft 365
We have recently upgraded to Exchange 2019 and looking to leverage OAuth with our Microsoft 365 tenant. The calendaring is not working with Teams and the hope is this will resolve these issues with meetings and writing back to the exchange on premise calendar. Will OAuth complete this task without requiring the Hybrid Configuration Wizard needing to be ran? Second, we have two tenants. If we configure OAuth with the one tenant, will this have any impacts to the functionality of the second tenant? All the users reside in the same AD and on the same exchange environment.1.1KViews0likes1Comment
Recent Blog Articles
No content to show