New-UnifiedGroup

same issue

Hi Rising Flight

Thank you for posting your question in the Microsoft Q&A forum.

Based on your description, I understand that the error message 'The group can't be created' despite the command returning partial output typically occurs when the initial group object is successfully created in Entra ID (Azure AD), but a subsequent step in the provisioning process fails. This is often due to a naming conflict or a violation of policy.

A key indicator is the name myxxx_xxxx-xxxx-xxxx-xxxx-xxxx, Exchange tried to create the group using the alias myxxx, but encountered a conflict. It attempted to resolve the issue by appending a GUID, yet the creation process still ultimately failed.

(Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.)

• Naming Conflict

The -Alias "myxxx" or the derived email address ******@mydomain.com is likely already in use by another object in your organization. This includes active user mailboxes, shared mailboxes, distribution lists, other Microsoft 365 groups, or even soft-deleted mailboxes. The alias must be unique; you can try to verify whether the alias or email address is already in use by running the following command in Exchange Online PowerShell:

Get-Recipient -Identity "myxxx"

If this command returns any object, you have a conflict. You must choose a different, unique alias for your new group.

• Group Naming Policy

Your organization may have a group naming policy that requires group names to follow a specific format (e.g., using a prefix or suffix like GRP-myxxx) > your chosen name myxxx does not conform to this policy. To check for potential naming policy restrictions, you can try to run the following command to view the policy details:

Get-OrganizationConfig | Format-List GroupNamingPolicy

If a policy is in place, adjust your -DisplayName and -Alias to comply with its rules.

• Permissions and Creation Policies

While you can run the cmdlet, your account might be restricted from creating groups by a policy. Some organizations limit Microsoft 365 Group creation to members of a specific security group. To confirm your ability to create Microsoft 365 Groups, please check with your Microsoft 365 administrator to ensure your account has the required permissions.

I hope this information proves useful to you. If there’s anything else I can assist you with, please feel free to leave a comment.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

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.

I have the same problem. This started between 09/25/25 (last successful run) and 09/30/25 (first failed run). I tried the most basic command with a random name, logged in as Global Admin, and it still doesn't work. It´s exclude Naming conflict, Naming Policy and Permission problem. See:

PS> New-UnifiedGroup -Displayname "Teste7489279"

Name DisplayName GroupType PrimarySmtpAddress

Teste7489279_3cc991e5-1c3f-43c4-abea-6f0c1d187006 Teste7489279 Universal ********XXXXXXXXmydomain

Write-Error: Microsoft.Exchange.Configuration.Tasks.TaskException: The group can't be created at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception,

ErrorCategory category, Object target, Boolean reThrow, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory

category, Object target, Boolean reThrow) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(LocalizedException exception, ExchangeErrorCategory category, Object

target) at Microsoft.Exchange.Management.RecipientTasks.NewUnifiedGroup.CreateUnifiedGroup() at

Microsoft.Exchange.Management.RecipientTasks.NewUnifiedGroup.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__118_1() at

Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)

Known issue:

Some admins using PowerShell to create unified groups may receive an error indicating creation failure

Issue ID: EX1177475

Affected services: Exchange Online

Status: Service degradation

Issue type: Advisory

Start time: Oct 22, 2025, 2:01 AM EDT

User impact

Admins using PowerShell to create unified groups may receive an error indicating creation failure.

More info

Despite the error message, group creation doesn't actually fail for admins and the groups are viewable in the admin center.

Scope of impact

Impact is specific to some admins who are served through the affected infrastructure, attempting to use PowerShell to create unified groups.

Current status

Oct 22, 2025, 4:51 AM EDT

We’re continuing to review reproduction details, support provided information, and error logs to help identify the root cause and develop a mitigation plan.

Next update by:

Wednesday, October 22, 2025 at 2:00 PM EDT