Skip to content

Latest commit

 

History

History
63 lines (45 loc) · 2.88 KB

issue-with-add-recipientpermission-cmdlet.md

File metadata and controls

63 lines (45 loc) · 2.88 KB
title description author ms.author audience ms.topic manager ms.custom localization_priority search.appverid appliesto ms.date ms.reviewer
You can't use the domain when you run the Add-RecipientPermission cmdlet
Describes an error message that you receive when you run the Add-RecipientPermission cmdlet in Exchange Online if the proxy address of the recipient uses a domain that isn't configured as an accepted domain. Provides a solution.
cloud-writer
meerak
ITPro
troubleshooting
dcscontentpm
sap:Migration
Exchange Online
CSSTroubleshoot
Normal
MET150
Exchange Online
01/24/2024
v-six

(You can't use the domain because it's not an accepted domain for your organization) error when you run the Add-RecipientPermission cmdlet

Problem

Scenario 1

When you try to run the Add-RecipientPermission cmdlet in Exchange Online, you receive the following error message:

You can't use the domain because it's not an accepted domain for your organization.
CategoryInfo : NotSpecified: (:) [Add-RecipientPermission], NotAcceptedDomainException

Scenario 2

When you try to run the New-MoveRequest cmdlet in Exchange Online, in order to move a mailbox from on-premises to Exchange Online, you receive the following error message:

You can't use the domain because it's not an accepted domain for your organization.
CategoryInfo : NotSpecified: (:) [New-MoveRequest], NotAcceptedDomainException

Scenario 3

When you create a migration by using New-MigrationBatch command or from Exchange Online Exchange Admin Center, in order to move a mailbox from On-Premises to Exchange Online, after a while the migration will fail. And you'll see the following output on the ErrorSummary when you run:

Get-MigrationUserStatistics User1@contoso.com | fl

You can't use the domain because it's not an accepted domain for your organization.

Cause

The proxy address of the recipient uses a domain that isn't configured as an accepted domain in the organization.

Solution

Do one of the following:

More information

Still need help? Go to Microsoft Community.