Never reach to be verified by Linkedin (Unlock $1,000 in Azure credits Get verified to unlock your credits)

Hello**Freddy Beltran,**

Greetings! Thanks for raising this question in the Q&A forum.

The "BadRequest (Conflict)" error you are seeing comes back from the LinkedIn OAuth callback used by the Founders Hub startup credits verification flow. This is not something wrong with your LinkedIn account or a step you are missing. It is a known backend issue where the Conflict response is returned because of an orphaned or mismatched LinkedIn identity record tied to your Microsoft account from a prior attempt, or a state mismatch between the Azure portal session and the LinkedIn callback. Multiple other users have hit this exact error on the same "Unlock $1,000 in Azure credits" verification step, and it is not resolvable through normal portal troubleshooting on your end.

Here is what to try, in order:

Clear the session state before retrying. Sign out of the Azure portal completely, revoke the Microsoft for Startups app permission on the LinkedIn side (LinkedIn Settings > Data privacy > Other applications), and clear cookies for both portal.azure.com and linkedin.com. Then sign back in to the Azure portal and attempt the LinkedIn verification again in a fresh browser session or an incognito/private window.

Confirm you are using the exact account the credits are tied to. The Microsoft account (MSA) you use to sign in to the Azure portal must be the same one associated with your Founders Hub enrollment, and the LinkedIn account you verify with should not have been used for a prior failed verification attempt on a different Microsoft account.

Try a different browser or device to rule out a cached OAuth state token causing the conflict.

If the error persists after the above, this needs backend intervention and cannot be fixed from the portal. Open a support request through Founders Hub rather than the general Azure support path, since this flow is owned by the Startups team. Go to the Founders Hub portal, select Support, and file a ticket under Benefits or Offers / Entitlement, explicitly stating that the LinkedIn verification callback returns {"error":{"code":"BadRequest","message":"BadRequest (Conflict)"}} and that this indicates a backend identity conflict, not a user-side eligibility issue. Include the Microsoft account email, the LinkedIn account email, and the approximate date and time of a failed attempt.

If the ticket gets closed without resolution or routed back to the same broken flow, reply on the ticket explicitly asking for escalation to the Founders Hub engineering team, since generic tier-1 support agents have not been able to resolve this pattern for other reporters either.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.