'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix New-Mailbox -Shared Active Directory Attribute Error in Exchange Online
Question details
The user encounters an Active Directory attribute error when attempting to create a shared mailbox using the New-Mailbox -Shared PowerShell command, even though web interface creation works perfectly.
- Product
- Exchange Online PowerShell
- Device & OS
- Windows
- Scenario
- Creating a shared mailbox using the New-Mailbox -Shared command in a cloud-only Exchange Online environment.
- Observed behavior
- The PowerShell command fails with an Active Directory operation or attribute conversion error despite the environment being purely cloud-based, which may be caused by regional settings or module parsing issues.
Ensure you have the latest version of the ExchangeOnlineManagement module installed and that you have active Exchange Administrator privileges in your Microsoft 365 tenant.
Run the Command in an English Windows Environment
Bypass regional parsing issues by executing the command on a system configured with English (US) language and keyboard settings.
In many cases, the Active Directory attribute error triggered by Exchange Online commands (like New-Mailbox or New-DkimSigningConfig) is caused by localization bugs in PowerShell. Changing your operating system language and keyboard to English often resolves parameter parsing conflicts.
Press Windows + I to open Settings, then navigate to Time & Language > Language.
Click 'Add a language', search for 'English (United States)', install it, and set it as your Windows display language.
Ensure the active keyboard layout in the system tray is set to US English.
Restart PowerShell, reconnect using Connect-ExchangeOnline, and run the New-Mailbox -Shared command again.
Update ExchangeOnlineManagement Module
Ensure that your Exchange PowerShell module is up to date to prevent bug-related attribute errors.
Use the Microsoft 365 Admin Center
If PowerShell continues to fail due to local environment issues, use the web GUI to create the shared mailbox as a reliable workaround.
Manage Your Office Documents Seamlessly with WPS Office
While troubleshooting Exchange Online issues, you can rely on WPS Office for your local and cloud document management needs. It is a highly compatible, free, and lightweight alternative to Microsoft Office that perfectly supports Word, Excel, and PowerPoint formats.
Frequently Asked Questions
Why does the New-Mailbox command fail in PowerShell but work in the web admin center?
PowerShell parameter parsing can sometimes conflict with local Windows language or keyboard settings, causing attribute conversion errors before the command even reaches Microsoft's servers. The web admin center bypasses your local OS regional settings.
Does this Active Directory attribute error mean I have an on-premises sync issue?
Not necessarily. This specific error frequently occurs in entirely cloud-based Microsoft 365 tenants without any on-premises Exchange servers, usually due to Exchange Online PowerShell bugs or Windows localization parsing issues.
How do I check my current ExchangeOnlineManagement module version?
Run the command 'Get-Module -Name ExchangeOnlineManagement -ListAvailable' in PowerShell. This will display the current version installed on your system. Keeping this module updated can prevent known command bugs.
What should I do if changing the Windows language doesn't resolve the PowerShell error?
If the issue persists in a cloud-only tenant and your module is fully updated, open a Microsoft support request directly from your Microsoft 365 Admin Center. Be sure to include your module version, tenant details, and the full red error output.
