Share via

Microsoft Customer Agreement Bulk Attestation Tool FAQ

Appropriate roles: Admin agent | Sales agent

The Microsoft Customer Agreement Bulk Attestation Tool is a console application designed to enable partners to retrieve the list of customers for whom they have an action pending in terms of attestation of the Microsoft Customer Agreement. This document outlines some of the frequently asked questions users of the tool might have. Effective October 7, 2025, the tool cannot be used to perform attestations on behalf of the customer and will be restricted to a read only capability.

General

Who can perform operations with the tool?

Any user with the Global Admin or Admin agent role in Partner Center can use the tool.

I made a mistake in one of my attestations. How do I fix the data since the customer record no longer shows in my fetched data?

You can use Partner Center or the Partner Center Create Agreement API to update the attestation details. The tool would no longer be able to successfully fetch/update the affected customer record once it's processed.

I tried the bulk tool to retrieve my customers and I don't see some of them. Why is that?

Not all customers require action. Your customers who accepted a Microsoft Customer Agreement prior to April 1, 2023, must review and accept the new terms as soon as possible to maintain up to date agreements with Microsoft. The bulk tool's fetch operation returns the customers in scope. Customers in scope are also marked on their individual account pages.

Alternatively, you can also determine which customers require action through the customer's account page in Partner Center. A notification appears on the customer's account page shows a prompt when agreement action is required.

I directed my affected customers to the Microsoft Admin Center to accept the Microsoft Customer Agreement, but they don't see an option to accept, or receive an error. How can they accept the agreement?

There are certain conditions that can cause an inability for the customer to directly accept the MCA. In such cases, the partner must provide an attestation for the customer. For more information, please see How to confirm that your customer accepted the Microsoft Customer Agreement.

Once the ability to do bulk attestations is removed on October 7, 2025, how can the tool be used?

The tool can still be used to identify customers that need to reaccept the MCA before October 7, 2025 to avoid any blocking actions. Once you have identified a customer that needs to reaccept the MCA, you will need to either direct them to self-accept the MCA at the Microsoft 365 admin center or you can attest for that customer using the attestation API or the Partner Center UX.

Troubleshooting guidance and error messages

How can I get more details on errors before contacting Partner Center support?

You can view the log files in the Logs folder in the tool's root directory. The log file name is formatted as: log_{MM-dd-yyyy_HH-mm-ss}.txt.

The default log level is Information. You can change the log level to Debug by passing in the runtime argument debug when running the tool. For example, dotnet run -- debug.

A selection of common errors and their resolutions are listed below.

Exception message: `Partner account is not MFA enforced`.

This error occurs when the account used to run the tool wasn't enrolled in MFA. MFA is required to access Partner Center Customer Workspace APIs. Enroll the account in MFA and try again.

If your partner organization was previously granted an MFA exception by Microsoft, run the tool using dotnet run -- noMfa to bypass the MFA check.

Authentication error: "AADSTS50011: The redirect URI 'http://localhost:(PORT)' specified in the request does not match the redirect URIs configured for the Application ID"

Screenshot of the Sign in page, with a message about the redirect URI.

This error occurs when the platform configurations and/or their redirect URIs for your application aren't configured correctly. Ensure that the redirect URIs for your application are configured to include http://localhost on the Mobile and desktop applications platform.

To learn more, see Microsoft Customer Agreement Bulk Attestation Tool: Prerequisites.

API Call error: `Failed to dispatch requests for records with status code: (STATUS CODE)`

The error message can vary depending on the status code of the API call. Here are some common status codes:

  • 400 - Bad Request. This error generally occurs when there's an issue with the data inputted into the CSV file. More detailed information can be found in the log file. For example, the following error message from the log file indicates that at least one of the email addresses in the customer agreement records to be updated by the bulk tool was invalid.

Error as shown in the tool output:

Screenshot of the Bulk Attestation Tool, with the error: 400 bad request.

Error details as seen in the log file:

Screenshot of the log file, with the message: Customer email is invalid.

  • 403 - Forbidden. This error generally occurs when the account used to run the tool does not have the appropriate permissions to perform the operation. Ensure that the account used has the Global Admin or Admin Agent roles. Post October 7, 2025, any calls to the tool to update the attestations for the customer will also result in a 403 error.

  • 500 - Internal Server Error. This error generally occurs when there's an issue with Partner Center APIs. Try again later or reach out to Partner Center support for assistance.

Related content

  • For additional help, contact support