Extension attributes with Cloud Identity Provider

[DBrowning]

I'm pretty sure I know the answer, but can't find the statement in any documentation.  Is it possible to pull attributes when you have Cloud Identity Provider enabled for Azure in via extension attributes?  If so, what attributes are available?

[stevewood]

Yes, you can pull extended attributes from Azure AD into an Extension Attribute. I used the Microsoft Graph Explorer to find a weird attribute (proxyAddresses), one that I knew would not be in Jamf Pro, put it into an Extension Attribute and the info was pulled back.

[DBrowning]

Do you have Azure setup under LDAP servers or Cloud Identity Provider?

[stevewood]

CIP... I have no LDAP servers configured in the server I was testing with.

[DBrowning]

Interesting....mine won't pull anything in.....

[stevewood]

Are you verifying the attribute you are pulling from has data via the Microsoft Graph Explorer first? And then I have to ask it, you are updating inventory on the device, right? ;-)

[DBrowning]

yes and yes!  I noticed using the graph explorer, if you use v1 there is very limited info.  If I switch to Beta i get a lot more data (including the proxyAddresses which is not returned on v1).

[stevewood]

The only other thing I can think is that you still have an LDAP server configured. I believe that an LDAP server takes precedence over CIP. I had my Okta dev account configured under LDAP and when I tried to pull info it would pull from Okta and not Azure. So I deleted the Okta LDAP setup and CIP took over.

Worst case, you can open a support ticket and they should be able to assist.

[DBrowning · Accepted solution]

Figured it out.  I had a bad EA asking for something that wasn't permitted.  Removed that EA and now I'm getting data!!