[Bug - Partner Center] Individual Edge developer enrollment fails and no support workspace is available

[shenaixie]

Describe the bug

I cannot complete enrollment in the Microsoft Edge extension developer program using an Individual account.

On the developer agreement page, clicking "Accept and continue" returns:

"Something went wrong. Please try again. If the problem persists, contact Microsoft support."

I also cannot create a Partner Center support request because the Workspace dropdown is empty and displays "No results found".

Correlation IDs:

• 8a4dae62-f615-4a86-81ab-e95d6586eb9a
• af1419e7-02c7-4571-bdee-39f313092b35
• f5045bec-9a2c-492b-bacc-041e9c77ee80

To Reproduce

1. Sign in to Microsoft Partner Center with a personal Microsoft account.
2. Open Account settings.
3. Open Programs.
4. Select Microsoft Edge and start enrollment.
5. Select Individual account and complete the required contact information.
6. Accept the Microsoft Edge developer agreement.
7. Click "Accept and continue".
8. The enrollment fails with "Something went wrong".
9. Open Help + support.
10. The Workspace dropdown displays "No results found", so a support request cannot be submitted.

Expected behavior

The Individual Microsoft Edge developer enrollment should complete successfully.

If enrollment fails, Partner Center should provide a working support channel even when the account does not yet have a workspace.

Please inspect or reset the Microsoft Edge program enrollment state associated with my Partner Center account.

Screenshots

I have attached:

1. The developer agreement enrollment error showing the Correlation ID.
2. The Partner Center support form showing "No results found" in the Workspace dropdown.

Desktop

• OS: Windows 11
• Browser: Microsoft Edge
• Version: Latest stable version

Troubleshooting already attempted

• Used Microsoft Edge InPrivate mode.
• Cleared Partner Center cookies and browser cache.
• Disabled browser extensions.
• Switched Partner Center language to English.
• Signed out and signed in again with the same personal Microsoft account.
• Retried enrollment at different times.

The problem still occurs.

[Rahul-Bauri]

Hi shenaixie
Please provide the account details from which you are trying to enroll and the HAR file captured while experiencing the above error. Additionally, when enrolling in the Edge program, please ensure the following requirements are met:

Enroll in Microsoft Edge using the following link: https://go.microsoft.com/fwlink/?linkid=2099798&ref=pcp

Please ensure that you sign in with a personal Microsoft Account (MSA) and complete the enrollment in an Incognito/InPrivate window. Please note that Edge enrollment does not currently support AAD (tenant-based) accounts.

Refer to the below documentation for any specific details:
https://learn.microsoft.com/en-us/microsoft-edge/extensions/publish/aad-account

[hannadevtools]

Before attaching a full Partner Center HAR, please sanitize and review it locally: it may contain Microsoft account cookies, Authorization headers, contact details, and request bodies.

ReqRescue is an open-source browser-local HAR sanitizer/analyzer I built for this kind of support handoff. It uploads 0 bytes, redacts secret values, groups the failed requests, and exports a Markdown incident report while keeping useful request structure. The 15-second demo is synthetic:

https://app.reqrescue.workers.dev/?utm_source=github_edge678&utm_medium=issue_comment

I would still review the sanitized file before sharing and make sure the correlation IDs Microsoft requested remain present. If you try the demo, I would value one sentence about anything unclear or missing.

[shenaixie]

Hi Rahul-Bauri,

I retried the enrollment using a newly created personal Microsoft Account with an @outlook.com address, in an Edge InPrivate window, using the enrollment link you provided.

The enrollment still failed after clicking "Accept and continue".

Account type: Personal Microsoft Account (MSA)
Enrollment mode: Edge InPrivate
Website: https://www.locknary.com/
Correlation ID: d2a71661-5155-4735-bcb4-6506695213c4

I have attached a sanitized HAR containing only the failed enrollment request. Personal contact details, address, phone number, cookies, credentials, and session values have been removed or redacted, while the request path, HTTP status, error response, and Microsoft correlation metadata were preserved.

Please let me know if you need the complete account email through a private support channel.

partner.microsoft.com.sanitized-for-microsoft.zip

[shenaixie]

Hi @Rahul-Bauri,

I retried the enrollment using a newly created personal Microsoft Account with an @outlook.com address, in an Edge InPrivate window, using the enrollment link you provided.

The enrollment still failed after clicking "Accept and continue".

Account type: Personal Microsoft Account (MSA) Enrollment mode: Edge InPrivate Website: https://www.locknary.com/ Correlation ID: d2a71661-5155-4735-bcb4-6506695213c4

I have attached a sanitized HAR containing only the failed enrollment request. Personal contact details, address, phone number, cookies, credentials, and session values have been removed or redacted, while the request path, HTTP status, error response, and Microsoft correlation metadata were preserved.

Please let me know if you need the complete account email through a private support channel.

partner.microsoft.com.sanitized-for-microsoft.zip

Correction to my previous comment:

The Correlation ID I previously provided was incorrect.

The Correlation ID displayed on the enrollment error page is:

d2a71661-5155-4735-bcb4-6506695213c4

The HAR contains these related request identifiers:

• mise-correlation-id: 2e277cea-17da-4fc4-88c6-8d1c074f8ef5
• ms-correlationid: 4b5567e5-406a-4d07-ac8c-b75087894e7a
• Trace ID: 20da8996413f459481672ba1bce2d33f

Please use these corrected identifiers for the investigation. Sorry for the confusion.

[hannadevtools]

I inspected only the sanitized HAR attached above. The 400 is more specific than the generic enrollment page suggests:

• There is one relevant request: POST /en-us/dashboard/account/exp/api/developer/enroll/msedgeaddons.
• It returns HTTP 400 after about 10.1 seconds.
• The response identifies AMSProvider:UpdateAccount, marks the error non-retryable, and reports downstream dependency ONEVET error 2105.
• The downstream model validation says both BusinessProfile.Address.City and UserProfile.Address.City are required.
• The request JSON does contain a top-level address.city field (its value is redacted in the published HAR), but it contains no businessProfile or userProfile objects.

That points to an enrollment payload / backend mapping mismatch, rather than a browser-cache or MSA-vs-AAD problem: the Individual enrollment UI appears to submit one top-level address, while the downstream update path expects the city to be populated under both profile models (or the server is failing to map the submitted address into those models). Because the response explicitly says isRetryable: false, repeating the same InPrivate flow is unlikely to change this specific failure.

A focused maintainer check would be to inspect the request mapping for Individual MSA enrollment and verify that the submitted address.city reaches both profile models before the ONEVET call. The correlation IDs already posted should make that server-side traceable.

The published sanitization looks careful: I found no email-shaped values, bearer tokens, or JWT-shaped values; the useful field names, status, response error, and correlation headers remain.

One transparency question for product research: was this HAR sanitized with ReqRescue after my earlier comment, or manually/with another tool? I cannot infer that from timing or filename and will not count it as ReqRescue usage without your confirmation. Either answer is useful; no endorsement is being requested.

ReqRescue production update: this attached BOM-prefixed HAR exposed two gaps in ReqRescue itself: byte-order-mark parsing and useful error metadata hidden inside an otherwise stripped JSON response body. Both are now fixed in production. Dropping the same file into ReqRescue now surfaces the two city validation paths, ONEVET, downstream HTTP 400, code 2105, provider, and retryability while still stripping the raw request/response bodies. Thank you for publishing a sanitized real-world reproduction.

[Rahul-Bauri]

Hi shenaixie,

Thanks for providing the requested details. I have shared them with the relevant team for further investigation to help unblock the issue. I’ll keep you updated as soon as I hear back from them, or if we need any additional information from your side to assist with resolving the issue.

Thank you for your patience and understanding.

[Rahul-Bauri]

Hi shenaixie

Seems like you are not providing the City while enrolling in the registration form. Please check and provide the screenshot if you are providing the city field.

Please share us a screenshot from the legal info page, the Edge registration page and a new HAR file to proceed further with the investigation. Thanks.