Others

Fix Cannot Create Shared Mailboxes or Aliases in Microsoft 365

Jason MillerJason Miller Nov 3, 2026 869 views

Question details

Users encounter a parameter error when attempting to create shared mailboxes or aliases in a new Microsoft 365 tenant.

Fix Cannot Create Shared Mailboxes or Aliases in Microsoft 365
Product
Microsoft 365
Device & OS
not provided
Scenario
Creating new shared mailboxes or aliases for a newly set up Microsoft 365 tenant environment.
Observed behavior
The system throws an error stating "A parameter cannot be found that matches parameter name 'Alias'," blocking the mailbox or alias creation despite using default Exchange administrator roles.
Before you start

Ensure you have your Microsoft 365 Global Administrator credentials ready and can successfully access the Exchange Admin Center.

Solution 1Recommended

Create a Custom Exchange Administrator Role

Bypass bugged default permissions in new tenants by manually creating a new administrator role with specific email-management privileges.

In new Microsoft 365 tenants, default roles like Exchange Service Administrators or Organization Management may fail to apply properly due to backend provisioning delays.

Creating a fresh role group forces the system to apply the necessary recipient-management permissions to your administrative accounts.

1
Open Exchange Admin Center

Log in to the Microsoft 365 admin center, navigate to the left menu, and select 'Exchange' under the Admin centers section.

2
Navigate to Roles

Go to the Roles section in the Exchange Admin Center and select 'Admin roles' to view the current permission groups.

3
Create a New Role Group

Click 'Add role group', give it a clear name (such as Custom Mailbox Admin), and add the required email-management and recipient roles from the list.

4
Assign Global Admins

Assign your Global Administrator accounts as members to this newly created role group, save your changes, and wait a few minutes before trying to create a mailbox alias again.

Create a Custom Exchange Administrator Role
Immediate Resolution: Applying custom roles often immediately resolves the alias parameter error without waiting for default tenant synchronization.
Free Microsoft Office alternative

Enhance Your Daily Productivity with WPS Office

While Microsoft 365 is essential for enterprise email hosting and Exchange management, you don't always need an expensive subscription for everyday document tasks. WPS Office provides a free, lightweight, and powerful alternative for editing documents, spreadsheets, and presentations.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install WPS Office: Run the setup file and follow the on-screen prompts to complete the lightweight installation process.
  3. 3. Open Your Documents: Launch WPS Office and open your existing Microsoft Word, Excel, or PowerPoint files without losing any formatting.
Fully compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Lightweight design ensures fast launch times even on older devices.Familiar ribbon user interface allows for immediate and seamless migration.Feature-rich PDF editing and conversion tools built directly into the suite.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 say a parameter cannot be found for 'Alias'?

This error typically occurs in newly provisioned Microsoft 365 tenants when the default Exchange Administrator or Organization Management roles have not synchronized correctly on the backend, stripping your account of the proper recipient-management permissions.

Do I need special permissions to fix Exchange role issues?

Yes. You must be signed in with an account that has Global Administrator privileges to create new role groups or modify existing administrative permissions in the Exchange Admin Center.

How long does it take for new Exchange permissions to apply?

Usually, newly assigned Exchange admin roles take effect within a few minutes. However, in rare instances involving Microsoft 365 server delays, backend synchronization can take up to 24 hours.