"Object couldn't be found" error when you run cmdlets in a remote PowerShell session in Office 365 dedicated


When you run available cmdlets in a remote PowerShell session against mailboxes other than your own in Microsoft Office 365 dedicated, you receive an error message that resembles the following:
The operation couldn't be performed because object 'John' couldn't be found on '0XX-NA1DC-001.0XXD.mgd.msft.net'.
+ CategoryInfo          : NotSpecified: (0:Int32) [Set-Mailbox], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : 78259DFD,Microsoft.Exchange.Management.RecipientTasks.SetMailbox


This issue occurs if one or both of the following conditions are true: 
  • The user does not exist, or the identity parameter was entered incorrectly.
  • The scope of the role group that grants you permission to run the cmdlet does not include the user.


To resolve this issue, follow these steps:
  1. Make sure that the identity parameter that was provided is entered correctly and that the identity parameter represents a valid user or a valid object.
  2. Make sure that you are a member of the appropriate Self-Service Role Based Access Control (RBAC) groups before you run the cmdlet against an organization-wide scope.  

    Note A significant number of cmdlets and parameters are available to all users. The cmdlets and parameters have an execution scope of "self" as part of the default role assignment policy. This behavior lets each user manage his or her own mailbox and distribution groups. The cmdlets and parameters that are provided by this policy are restricted to "self." In this situation, the error that's mentioned in the "Symptoms" section is generated when you try to run the cmdlets on objects outside the scope of "self." 

More Information

For more information about role assignments policies, go to the following Microsoft TechNet website:
For more information about the available Self-Service RBAC groups, see the following Self-Service administration guide:


文章識別碼:2838124 - 最後檢閱時間:2016年1月15日 - 修訂: 1