Store developer account creation fails – INTERNAL_ERROR (PartnerIntegrationService 400)

Question

Store developer account creation fails – INTERNAL_ERROR (PartnerIntegrationService 400)

matias alia 20

Hi, I'm registering a free individual Microsoft Store developer account from Argentina. Identity verification completed and my address shows as verified, but account creation always fails at the final step. POST https://storedeveloper.microsoft.com/api/onboarding returns 400: - code: INTERNAL_ERROR - error: "PartnerIntegrationService call failed: Request failed with status code 400" - correlationId: [Moderator note: Personally Identifiable Information removed] - Date: Tue, 27 Oct 2026 20:59:59 GMT Already tried: retrying, incognito, clearing cookies, reviewing all fields (name matches ID). Could you please check this on your side? Thanks.

0 comments

Answer accepted by question author

Liora 3,285 Independent Advisor

Dear @matias alia,

Thank you for providing the detailed error information, including the correlation ID and the troubleshooting steps you have already performed.

Based on your description, the fact that your identity verification and address verification have already completed successfully suggests that the failure is occurring during the account onboarding process itself rather than during the verification stage.

Since the request is consistently failing with:

INTERNAL_ERROR

PartnerIntegrationService call failed: Request failed with status code 400

and you have already tested retries, incognito mode, cookie clearing, and verified that your registration details are correct, this does not appear to be a typical browser or client-side issue.

For this type of Microsoft Store Developer account onboarding problem, I would recommend contacting the Microsoft Store developer support team directly using the official contact options provided here: Need help? Contact us

Since this appears to involve the backend onboarding workflow, the Store developer support team is in the best position to investigate the failed PartnerIntegrationService request and determine whether there is a problem with the account provisioning process.

I hope this helps point you to the appropriate support channel, and I wish you the best of luck getting the account created successfully.

Warm regards,

If the answer is helpful, please select "Yes, accept answer". If you have any questions or new updates, please feel free to comment below.

0 comments

1 additional answer

Your answer

Answer 1

Email [Email] with the failed request details; Microsoft designates this mailbox specifically for problems with the new zero-fee individual developer onboarding process.^1^

What to include

Send the report from the same personal Microsoft account used for registration, and include:

Account type: Individual developer
Country/region: Argentina
Exact error:
- HTTP 400
- Code: INTERNAL_ERROR
- Message: PartnerIntegrationService call failed: Request failed with status code 400
The correlation ID shown in the response
Failure timestamp, explicitly marked as UTC/GMT
Confirmation that identity and address verification completed
A screenshot of the final error
Browser network trace or HAR file, if available
The onboarding URL and a note that the failure occurs on the final POST /api/onboarding

Do not send passwords, authentication tokens, cookies, session headers, full ID images, or other identity documents unless Microsoft requests them through a secure support channel.

Suggested message:

Subject: Individual Store onboarding fails with PartnerIntegrationService 400

I am creating a free Individual Microsoft Store developer account from Argentina through the new onboarding flow. Identity and address verification complete successfully, but final account creation fails consistently.

HTTP status: 400
Code: INTERNAL_ERROR
Error: PartnerIntegrationService call failed: Request failed with status code 400
Correlation ID: [insert ID]
Failure time in UTC/GMT: [insert timestamp]

The failure occurs during POST /api/onboarding. Please trace the correlation ID and check whether the account is partially provisioned or whether the Partner Center integration rejected the request. A screenshot and network trace are attached.

Because retrying, clearing cookies, using an InPrivate/incognito session, and reviewing the fields have already made no difference, repeating those browser steps is unlikely to provide additional diagnostic information. The exact underlying cause cannot be confirmed from the HTTP 400 response alone; the correlation ID must be investigated by Microsoft.

One prerequisite to check only if applicable

An individual developer account must use a personal Microsoft account (MSA), and the supported zero-fee flow must begin at https://storedeveloper.microsoft.com.^2^

If the current sign-in is a work or school account, start once from that supported entry point with a personal Microsoft account. If it is already a personal account, do not create another account or restart identity verification unless support directs you to do so.

If the onboarding mailbox does not resolve it

Create a Dev Center support case through the Windows Developer Support route at https://aka.ms/windowsdevelopersupport. Microsoft lists this channel for Partner Center enrollment and account-management issues.^3^

Use the same evidence and correlation information in the case. Microsoft Q&A participants cannot access onboarding service logs or inspect the correlation ID.

If Partner Center already shows an Apps & Games workspace, mention that in the case as possible partial provisioning. Do not treat its absence as proof of the cause: the documented five-minute refresh guidance applies after account setup completes successfully, whereas this request failed before confirmed completion.^2^

References