Edit

The Act As Account Does Not Have Permissions to Create Items in this Folder

  • Article

Topic Last Modified: 2012-05-23

The Microsoft Remote Connectivity Analyzer sends a CreateItem XML/HTTP request to the Exchange Web Services service using the Exchange Web Services API to create a test item in a mailbox or public folder. When an access denied error status message is present in the response, the Microsoft Remote Connectivity Analyzer generates the following error:

"ErrorCreateItemAccessDenied, the Act As Account doesn't have permissions to create items in this folder."

The Microsoft Remote Connectivity Analyzer uses the CreateItem Operation of Exchange Web Services to create a mail message in a mailbox or public folder to test whether the account specified has permissions to write to the specified folder.

The "Act As Account" is the account used by Exchange to authorize the execution of Exchange Web Services commands. In most cases, it's the account issuing the Exchange Web Services requests; however, if ExchangeImpersonation (also known as Server-to-Server Authorization) is being used, then the account being impersonated is the "Act As account".

For More Information

To resolve this issue, the Act As account must have permission to create items in the folder specified. To make sure the Act As account has the appropriate permissions, perform the following steps:

  1. Grant the Act As account full mailbox permissions to the folder's mailbox via the Add-MailboxPermission command. Or, see How to Allow Mailbox Access.

  2. Grant the Act As account permissions to create items in the public folder via the Add-PublicFolderClientPermission command. Also, see Configuring Public Folder Permissions.

  3. Grant the Act As account permission to create items in the specified mailbox or public folder in Outlook by editing the Outlook folder permissions.

The Microsoft Remote Connectivity Analyzer has limited documentation at this time. To improve the documentation for each of the errors you might receive, we would like to solicit additional information from the community. Use the Community Content section to post other reasons why you failed at this point.  If you need technical assistance, create a post in the appropriate Exchange TechNet forum or contact support.