question

ohaya-4009 avatar image
0 Votes"
ohaya-4009 asked JamesTran-MSFT edited

AD Connect - How to provision into Azure AD?

Hi,

I am/was using FIM awhile ago (a long time ago), but now I am doing some work with trying to sync users FROM Oracle Unified Directory (OUD LDAP) into Azure AD using AD Connect. I hope that this is the correct place to post this?

We have the AD Connect installed, and connectors for both the OUD and to the Azure AD, but I don't understand how we can trigger provisioning into the Azure AD connector space and get the user information to export into the Azure AD?

In FIM, I know that to do that, we had to have some code in the MV Extension, but how do you do that now, in the AD Connect? I've been searching for information, and found lots of information about going the other way (from Azure AD into the MV), but not the opposite way (from MV into the Azure AD CS).

Thanks,
Jim

azure-ad-connectazure-ad-user-provisioning
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

ZollnerD avatar image
1 Vote"
ZollnerD answered JamesTran-MSFT edited

A quick note/warning: Usage of the Generic LDAP connector that you'd be using to connect to OUD is supported, but configuration assistance isn't something that our support teams can help with and you'd have to go through a consultant either externally or through Microsoft. ​Just a head up for you and others reading this - mechanical questions like this are pretty easy to address even here on Q&A, but questions about how to get started if you don't have a strong FIM/AADC background are better served by an implementation partner rather than support.


In this specific case I think you're pretty close.. to go between different points in AAD Connect/FIM - ie: AD/LDAP Connector Space -> Metaverse -> AAD Connector Space, you need "provision" type rules. You'll need two rules at the least - one inbound provision-type rule on the LDAP connector, which will take object data from OUD LDAP and put it into the metaverse. Then you'll need an outbound provision-type rule on the AAD Connector, which will take data out of the metaverse(hence outbound - it's from the perspective of the metaverse) and move it into the AAD Connector Space, at which point an export from the AAD connector will push data into AAD.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@ohaya-4009
I just wanted to check in and see if you had any other questions or if you were able to resolve this issue?


Thank you for your time and patience throughout this issue.


Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

0 Votes 0 ·