The Act As Account May Not Have Permissions to Access this Folder


Topic Last Modified: 2012-05-23

The Microsoft Exchange Analyzer Tool sends a GetFolder XML/HTTP request to the Exchange Web Services service using the Exchange Web Services API to get folder information for a mailbox or public folder. When an access denied error status message is present in the response, the Exchange Remote Connectivity Analyzer generates the following error.

"The Act As Account may not have permissions to access this folder."

The Exchange Remote Connectivity Analyzer uses the GetFolder operation of Exchange Web Services to get folder information for a mailbox or public folder to test whether the account specified has permissions to read folder information including the folder’s content items count.

The "Act As Account" is the account used by Exchange to authorize the execution of Exchange Web Services commands. In most cases, this is 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 read folder information for the folder specified. To make sure the Act As account has the appropriate permissions, do the following:

  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 read items in the public folder via the Add-PublicFolderClientPermission command. Also, for Exchange Server 2007 see Configuring Public Folder Permissions.

  3. Grant the Act As account permissions to read items in the specific mailbox or public folder in Outlook by editing the Outlook folder permissions.

The Exchange Remote Connectivity Analyzer is a new tool with limited documentation at this time. In an effort to improve the documentation for each of the errors you might receive, we would like to solicit additional information from the community. Please use the Community Content section below to post additional reasons why you failed at this point.  If you need technical assistance, please create a post in the appropriate Exchange TechNet forum or contact support.