Edge program registration blocked – 715-123225

If GitHub sign-in is acceptable and has not already been tried, restart Edge enrollment using Sign in with GitHub instead of signing in directly with the existing Microsoft account; this resolved the same Individual enrollment block and reference 715-123225 in a matching user report, although it is not a guaranteed Microsoft fix.^1^

Try the GitHub sign-in workaround

1. Sign out of Partner Center.
2. Open the Microsoft Edge developer registration page.
3. Select the GitHub sign-in option and authorize the account.
4. Complete the Edge registration again as Individual, selecting the country/region where you live.
5. Check whether enrollment completes and the Edge workspace appears.

Partner Center supports GitHub sign-in for Edge enrollment; an MSA is created for the GitHub account. Edge publishing requires an MSA as the Partner Center account’s Primary Owner.^2^

Use this only if creating that GitHub-associated Microsoft identity is acceptable. It may result in a different developer account from the one currently blocked.

If the block remains, request an account-specific review

This trust decision cannot be reviewed or removed through Microsoft Q&A. Submit a private Partner Center support request:

1. In Partner Center, select AI assistant in the upper-right corner, describe the enrollment block, and select Contact Support.
2. If AI assistant is unavailable, select Help (?) → Contact Support.
3. Select the Edge/Marketplace enrollment workspace and relevant registration problem type.
4. Choose Review solutions → Create support request.^3^

Include:

• Program: Microsoft Edge Add-ons
• Account type: Individual
• Country/region: Egypt
• Exact “Microsoft runs on trust” message
• Reference number and both correlation IDs from the failed attempts
• Date and time of the latest failure, including time zone
• Screenshot of the complete error page
• Confirmation that the failure occurs during enrollment, before extension submission
• The Microsoft account used for enrollment, entered only in the private support form

Do not post identity documents, email addresses, or account details in a public Q&A or GitHub issue. Supply identity documents only if Microsoft Support requests them through a secure channel.

The Edge documentation describes Individual verification as the shorter process involving publisher-display-name availability; the utility bills, DUNS records, and business-registration document process applies to company accounts, not automatically to an Individual enrollment.^2^

If Partner Center cannot create a ticket

The generic Partner Center support procedure is documented for work-account access, while Edge developer enrollment uses an MSA. If the support controls are unavailable or the mandatory Workspace list is empty because enrollment never created an Edge workspace, report the case on the MicrosoftEdge-Extensions repository’s Issues page. Microsoft explicitly permits that channel for inquiries about Edge Partner Center developer accounts.^4^

In that public issue:

• Include the reference number, error text, country, account type, and failure stage.
• State that Partner Center cannot create a support request because no workspace is available.
• Redact correlation IDs, email addresses, screenshots containing account data, and all identity documents.
• Ask for guidance or escalation to the appropriate account-review channel; GitHub maintainers should not be assumed to have the ability to unblock the account directly.

A current open report documents the same Individual enrollment failure, SessionValidationFailed, and reference 715-123225, so linking that matching report may help identify the incident pattern.^5^

References

1. Partner Center registration for an individual Edge developer ... - GitHub
2. Register as a Microsoft Edge extension developer
3. Get help and contact support in Partner Center
4. Contact the Microsoft Edge extensions team
5. #863 Bug - Partner Center Individual Edge Add-ons enrollment blocked (SessionValidationFailed, 715-123225)