Jump to content

Recommended Posts

Posted

This summer we have moved to Office 365 for our students (from local exchange) and everything seems to go well, except on first run Outlook was not auto-creating the Outlook account, after a bit of trial and error, some double-checking of autodiscover settings etc. it seems to be as simple as users not having the primary SMTP field populated within local AD.

 

Our process is:

 

Create users in local AD

This is synced with Office 365 using Azure AD Connect

Assign them a licence in Microsoft 365 (via script)

The above creates them their email account

 

I had presumed as we have Azure AD Connect the primary SMTP email would be written back to the local AD (which is where Outlook looks for the email address). Is this not the case? How do you manage this? Manually populate the email address field too when creating the account? Or should, as I suspect, it be syncing?

Posted

I may be wrong, as I have never fully got my head around this, but I think unless you have a hybrid setup this will not work. You need to have an onsite Exchange instance to have the Exchange schema extensions and to allow AD to be updated locally.

 

Or something like that.

Posted

ah, ok. I find that strange but that at least explains the problems I am getting.

 

Will look for a tool to auto-populate this. I am guessing it is just the AD email field I need.

 

- - - Updated - - -

 

Also, we have hybrid fully setup and everything else is working. Just not this.

Posted (edited)

I am sure you need to choose the additional attributes you want to be written back. In this case the SMTP address.

 

Just re read and saw you have hybrid exchange enabled.

My one definitely writes back the email to all new users.

 

Our process is the same as yours, except salamander provisions the mailbox using the same script as you would if you were to do it yourself.

Edited by mukz
Posted

AFAIK Azure AD Connect does not write back to locally hosted AD without a hybrid deployment or SSPR configured.

 

Maybe it's worth checking to see if the hybrid deployment is functioning properly?

 

Otherwise you could have a powershell script that auto-populates the email field after assigning the licences. You should be able to use the PowerShell AD provider to do this.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...