Google Azure AD Sync - Map custom attribute to put users in particular OUs in Google

[Colindean2000]

Anyone have any recent expertise with the new Azure AD Sync (Beta) functionality on Google?

 

I’ve setup the sync between Google and Azure AD, all working as expected.

 

What I’m not able to get working is the part that should read an attribute from AD and match that to an OU named the same on Google so as to keep users tidy in various OUs.

 

As an example I have an OU on Google called Students, it lives under the root domain name OU.

 

I’ve tried setting in AD on a user the following attributes: Department and/or ExtensionAttribute1 and have set both these to be Student however when I do a sync (with either attribute set in Google) it says skipping user as a matching OU name cannot be found in the attribute (does correctly list the attribute name in the log)

 

Not sure what I’m missing, any experts set this up recently and can offer any words of wisdom?

[steveg]

Not sure if you ever solved this, but having spent most of my Sunday morning trying to get it to work - the attributes are case sensitive, Azure uses lower case, so department would work but Department wont. The google docs use a capital letter but this is incorrect, in other documentation for attribute mapping they show it as lower case.

[jnfarmer]

Sorry to re-raise this thread, but did anyone have any luck with this? Specifically with extensionAttributes.

[bjohnny42]

It didn't for us using extension attributes, trying cases and variations on names etc. So just used Fax instead and worked . Azure name -   faxNumber

 

Remember to use a forward slash, so    students/Year07

 

Use Mail Enabled Security Groups in Microsoft for Group Transfer, they can be Security Groups for the provisioning.

[Frodo_Baggins]

I'm sure Google support told me we can't use extended attribute with their new sync so I just got salamander to map the path to another supported field and it works fine and then changed as bjohnny42 mentioned in workspace