question

IAMUser-9916 avatar image
0 Votes"
IAMUser-9916 asked YukiSun-MSFT commented

Removing exchange from FIM 2010 R2

I have a question in regards to the provisioning email addresses via FIM. Right now we have a hybrid environment where email address is created on prem. We then take that email and migrate it to the cloud.

we are exploring to do away of having email created on prem via FIM. Is it as simple as going under AD MA\configure extensions, to change the provision for dropdown to "No Provisioning" ?

Is there any impact to new users or existing?

The initial thought was to just add the license to the user and email is automatically created in the cloud rather than on prem via FIM.

Thank you,

office-exchange-server-administration
· 4
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.

Hi @IAMUser-9916,

As far as I know, FIM 2010 R2 has already ended its mainstream support and the according to the official document, it's now suggested to using AAD Connect for Azure AD synchronization in Exchange hybrid deployment.

But even with AAD Connect configured, it's still recommendeded to have new mailboxes created in the on-premises AD first, then add the lisence to the user after synchronization. This can avoid issues like incorrect or conflicting information. Here's a blog for your reference:
Creating an Office 365 Mailbox in a Hybrid Configuration
(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)

" It’s possible to simply create the Office 365 account in Active Directory, wait for AD Connect to sync the user to Office 365 and license the account. But creating new mailboxes this way never fills in the correct Exchange attributes on the user’s AD account, which causes them to not display in the local EAC.
This could also cause the inventory of your on-premises AD Connect domain and Azure AD domain to show incorrect data and conflicting information."


If an Answer is helpful, please click "Accept Answer" and upvote it.

0 Votes 0 ·

Thank you. I'm exploring of getting away from the hybrid environment. Exchange is the first in removing from the equation. However,
From the article you sent me, there was an excerpt from it that bothers me and I will need to research further:

It’s possible to simply create the Office 365 account in Active Directory, wait for AD Connect to sync the user to Office 365 and license the account. But creating new mailboxes this way never fills in the correct Exchange attributes on the user’s AD account, which causes them to not display in the local EAC.

This could also cause the inventory of your on-premises AD Connect domain and Azure AD domain to show incorrect data and conflicting information.

0 Votes 0 ·

Hi @IAMUser-9916,

I'm exploring of getting away from the hybrid environment. Exchange is the first in removing from the equation.

Do you mean you are planning to decommission your on-prem Exchange server and move to a full cloud implementation?

If this is the case, on the prerequisites that 1. all mailboxes have been moved to Exchange online, 2. you don't need to manage users from on-premises any longer, 3. there's no need for directory synchronization or password synchronization, then you should be able to safely disable directory synchronization and remove Exchange from the on-premises environment.

Here's an official document about decommission on-premises Exchange servers in Hybrid environment for your reference:
How and when to decommission your on-premises Exchange servers in a hybrid deployment


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



0 Votes 0 ·
Show more comments

0 Answers