Blog Post

Exchange Team Blog
1 MIN READ

Deprecation of Classic Exchange Admin Center (EAC) in GCC and GCC-H environments

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Jul 31, 2023

Today, we are announcing the deprecation of the classic Exchange admin center (EAC) in our GCC and GCC-H environments.

The modern EAC is already available in these environments and can be accessed at:

The classic EAC will be deprecated by August 30, 2023. After that date, admins in those environments will not be able to use the classic EAC.

The modern EAC offers an array of new features including a streamlined interface, enhanced performance, and security. We recommend admins in these environments transition to the modern EAC as soon as possible.

To learn more about the modern EAC, see Exchange admin center in Exchange Online.

Exchange Online Admin Team

Published Jul 31, 2023
Version 1.0

7 Comments

  • OskarMollersen's avatar
    OskarMollersen
    Copper Contributor

    RolandEhle: You might need to re-scope some permissions, but this is doable in Microsoft 365 Admin Center under Users > Active Users > Select User > Mail > "Manage automatic replies". Or there's always the option to use PowerShell: https://learn.microsoft.com/en-us/powershell/module/exchange/set-mailboxautoreplyconfiguration?view=exchange-ps 

  • RolandEhle's avatar
    RolandEhle
    Copper Contributor

    The possibility to set Out of Office replies for another user has been removed from the Exchange Admin Center without notification. This was a key feature for our colleagues with scoped permissions (Exchange roles). We currently have no idea how to bring this feature back.

  • cgdcms's avatar
    cgdcms
    Copper Contributor

    We have a hybrid environment where sync goes from on-prem to cloud. Groups are made and managed locally. When using the new EAC online and editing a group it says, "You can only manage this group in your on-premises environment. Use 'Active directory users & groups' or 'Exchange Admin Center' tools to edit or delete this group." An example of something we use the on-prem EAC is managing who can send to the group such as "All". What is the recommended way forward for this limitation?

  • Juergen_Brogmus's avatar
    Juergen_Brogmus
    Copper Contributor

    Newly I am getting this "Null Token" problem back. Once it came every 10 min, than after a long running support case tis was gone and now suddenly after doing something in the console (it was not idling for a long while) it reloads the console with this error 😕

  • Renat Matveev's avatar
    Renat Matveev
    Brass Contributor

    thejimmartin - It is completely opposite of I needed. I need give "Send as group" (security\distribution group from AD) rights for users. You are saying about giving a group Send as rights for user's mailbox.

    In Classic EAC it worked. In new EAC only useless banner "You can only manage this group in your on-premises environment. Use 'Active directory users & groups' or 'Exchange Admin Center' tools to edit or delete this group". It is still working via PowerShell, but not sure, will it survive after some other "modern update".

    Also, I can't use "MS 365" groups, because of complex infrastructure (Exchange\ExO\Linux mail servers with single shared between them domain)

  • Renat Matveev's avatar
    Renat Matveev
    Brass Contributor

    In hybrid environment is not possible to manage Send as\Send on behalf rights for AD-synced groups in Modern admin center. Classic EAC did it without any problems. Will it be fixed? Or we need always use PowerShell for management to be modern?