- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Azure sync question for anyone that can help
Posted on 2/5/24 at 12:39 pm
Posted on 2/5/24 at 12:39 pm
We are testing out Azure right now and have successfully synced our on premise AD with the Azure Cloud via the Entra ID connect utility. We are not seeing any sync errors but our updated on premise AD user data is not making it to the cloud.
Example:
We update a user's title, email group membership, etc. After performing either a Delta or full sync, those new changes do not show up in Azure for that user.
Anyone have any suggestions? I don't see any errors on either the cloud or on premise side.
Example:
We update a user's title, email group membership, etc. After performing either a Delta or full sync, those new changes do not show up in Azure for that user.
Anyone have any suggestions? I don't see any errors on either the cloud or on premise side.
Posted on 2/5/24 at 12:47 pm to BayouBengal51
What did MSoft say ? Not joking, we have a dept whos job is to go between
Posted on 2/5/24 at 12:53 pm to BayouBengal51
I've found the easiest way is to make sure that the user has a primary SMTP address associated with the account under the proxyaddresses attribute in Active Directory. Note that this is not the same thing as the email address field that you set when setting up a user, and it may have to be manually set under Advanced Features in Active Directory Users and Computers. Basically you add an entry to proxyaddresses in the format SMTP:user@domain.com. The upper case SMTP denotes that it is the primary address for the user. You can also have entries with lower case smtp, like smtp:user2@domain.com. The lower case smtp denotes that it's an alias address and not the primary.
Here's an article on various scenarios - LINK
Here's an article on various scenarios - LINK
This post was edited on 2/5/24 at 1:00 pm
Posted on 2/5/24 at 3:23 pm to GrammarKnotsi
quote:
What did MSoft say ? Not joking, we have a dept whos job is to go between
I was waiting on them to call me back when I made the post. Thy eventually got back to me, and we thought we had it fixed. We had a conditional policy causing some issues, but after that was resolved we still don't have the on-prem data syncing in correctly.
They are going to call us back after comparing some screenshots and config settings.
This post was edited on 2/5/24 at 3:28 pm
Posted on 2/7/24 at 8:38 am to jdd48
This is where I'd start as well. Called SMTP matching for anyone who wants to look up more about this.
Popular
Back to top
