locked
Moving into cloud RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all, 

    Thank you all for the help so far, just want to clarify a few minor details that is still tangled in my head. We are in the testing phase of migrating from on-prem exchange to exchange online.

    1. As we know the MsExch attributes are added into AD when a on premise exchange server is installed. Can i still manage these when i move to the cloud via shell if i decommission the on prem server? Am i correct in saying that these attributes are installed when on-prem exchange is installed? 

    2. This is a very stupid question, but i still want to just publish it in my head. If we started off with a Exchange online solution from Day 1, we wont have needed a on prem server, is that correct?

    3. I've read several articles which tell me not to de-commission our on prem exchange server. I understand that we would struggle with some administration if we go down this route. Now, is this because of the fact that we went into a hybrid solution first, before moving into cloud and it doesnt remove certain attributes completely, is this why decommissioning isnt a good idea?

    Many thanks in advance.

    Wednesday, November 28, 2018 12:53 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello ,

    1.When you directly create a mailbox in cloud you don’t have the options in cloud to map with the existing AD account in your on premises active directory . when the Mailbox is directly created in cloud , the corresponding AD account for that mailbox will be automatically created on the Azure AD .

     2.Let say you have used AD connect to sync the active directory account from your on premise AD to office 365 . The you can enable the mailbox in cloud for the synced AD account . So in that case if a password is changed for that AD account on premise AD the changes will get reflected to the mailbox created in office 365. Likewise you do have the option to enable the Password write back in AD connect . Once it is enabled then if we change the password for the Mailbox in office 365 then it will get synced to corresponding AD account which resides in on premise Active directory .

    Thanks & Regards S.Nithyanandham


    Wednesday, November 28, 2018 6:25 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi, 

    Many thanks for the reply. 

    Lets take an example, forget the whole on prem scenario. If we create a new mailbox on cloud who already has a AD account, can we link the existing AD username and password with that new mailbox? So, if we change the password locally, the password on the mailbox changes too. Is this possible? 

    Many thanks in advance.

    Addition information about it, if you have created mailbox in Exchange online rather than Enable-mailbox, you can use SMTP matching to match this Exchange online mailbox with on-premises user accounts. For more information about it, you can have a look about this article. 

    Regards,

    Kyle Xu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, November 29, 2018 9:58 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello ,

    1. As we know the MsExch attributes are added into AD when a on premise exchange server is installed. Can i still manage these when i move to the cloud via shell if i decommission the on prem server? Am i correct in saying that these attributes are installed when on-prem exchange is installed? 

    Generally, in your case hybrid migration requires AD connect for syncing the objects prior to mailbox migration. So you need at least one exchange server to manage synced objects in Exchange online.

    2. This is a very stupid question, but i still want to just publish it in my head. If we started off with a Exchange online solution from Day 1, we won’t have needed a on prem server, is that correct?

    If all your mailboxes are directly created in cloud (i.e cloud identity model) then you don't need to have the on premise exchange server for managing the cloud identities. You can directly manage all the mailboxes through office 365 admin center.

    3. I've read several articles which tell me not to de-commission our on prem exchange server. I understand that we would struggle with some administration if we go down this route. Now, is this because of the fact that we went into a hybrid solution first, before moving into cloud and it doesnt remove certain attributes completely, is this why decommissioning isnt a good idea?

    Let me explain you very briefly .Let's assume that you wanted to go for the hybrid migration .So in that case first you need to configure the hybrid setup between the your exchange on premise and office 365 .Once the HCW is completed then you need to install the AD connect on the premise environment to sync all the mailboxes from exchange on premise to office 365 .Once the sync is completed , you can see the mail user accounts in office 365 for all the mailboxes which is been synced from exchange on premise .Generally AD connect will do the sync for every 30 minutes by default .

    Now you are ready to perform the mailbox migration. Let’s say that you have started the mailbox migration by selecting the respective mail user object in Exchange online ECP console. Assume that the mailbox migration is completed successfully.

    Let me tell you what will happen next post migration. The mail user in the office 365 environment becomes as the mailbox and mailbox in the exchange on premise will become as mail user object.

    Now here the actual answer coming for your question but to understand my answer that you need to know all these entire story.

    Post mailbox migration to office 365, Assume that you wanted to do some changes on the mailbox. Let’s say you want to change the proxy/smtp address of the mailbox, so in that case generally persons will make use of the office 365 admin center or Exchange online ECP console to perform the changes. But as per the Microsoft design it will not allow you to perform the changes. This is not only for the proxy/Smtp addresses and it is applicable for most of the attributes. As because the mailbox in office 365 was synced and syncing through AD connect. You should re call my statement , remember post mailbox migration we have performed the AD connect full sync as the one of the prerequisites for hybrid migration.

    Generally Microsoft doesn't allow us to perform any changes directly on the synced objects through office 365 admin center or through Exchange online ECP console .So in that case we need to have at least one exchange server in on premise to perform the changes .I believe you could remember my statement , As I said earlier there will be mail user object in exchange on premise for the mailbox which was migrated to office 365 .So we need to perform the necessary changes on the mail user object through the exchange on premise server and those changes will be replicated to the migrated mailbox in office 365 through AD connect in next sync cycle .

    Thanks & Regards S.Nithyanandham


    Wednesday, November 28, 2018 1:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, 

    Many thanks for the reply. 

    Lets take an example, forget the whole on prem scenario. If we create a new mailbox on cloud who already has a AD account, can we link the existing AD username and password with that new mailbox? So, if we change the password locally, the password on the mailbox changes too. Is this possible? 

    Many thanks in advance.

    Wednesday, November 28, 2018 4:30 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello ,

    1.When you directly create a mailbox in cloud you don’t have the options in cloud to map with the existing AD account in your on premises active directory . when the Mailbox is directly created in cloud , the corresponding AD account for that mailbox will be automatically created on the Azure AD .

     2.Let say you have used AD connect to sync the active directory account from your on premise AD to office 365 . The you can enable the mailbox in cloud for the synced AD account . So in that case if a password is changed for that AD account on premise AD the changes will get reflected to the mailbox created in office 365. Likewise you do have the option to enable the Password write back in AD connect . Once it is enabled then if we change the password for the Mailbox in office 365 then it will get synced to corresponding AD account which resides in on premise Active directory .

    Thanks & Regards S.Nithyanandham


    Wednesday, November 28, 2018 6:25 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi, 

    Many thanks for the reply. 

    Lets take an example, forget the whole on prem scenario. If we create a new mailbox on cloud who already has a AD account, can we link the existing AD username and password with that new mailbox? So, if we change the password locally, the password on the mailbox changes too. Is this possible? 

    Many thanks in advance.

    Addition information about it, if you have created mailbox in Exchange online rather than Enable-mailbox, you can use SMTP matching to match this Exchange online mailbox with on-premises user accounts. For more information about it, you can have a look about this article. 

    Regards,

    Kyle Xu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, November 29, 2018 9:58 AM