Share via

Previously verified Microsoft for Startups account no longer shows earned Azure credits; sign-in triggers new application flow and BadRequest Conflict error

Emre Öcal 0 Reputation points
2026-06-01T20:49:50.9533333+00:00

Hello

I previously verified my startup through Microsoft for Startups and had earned Azure startup credits associated with my account. However, I am currently unable to see or access those credits.

When I try to sign in to the Microsoft for Startups / Azure startup credits account, I am redirected to the “Apply for Microsoft for Startups” screen as if I am a brand new applicant. The flow then asks me to verify my startup again through my LinkedIn account, even though I have already completed this verification before.

After attempting the verification flow again, I receive the following error:

code: "BadRequest" message: "BadRequest (Conflict)"

This looks like my existing verified startup profile or credits record may not be linked correctly to my current sign-in account, or there may be a duplicate application / verification conflict.

Could you please help me investigate and restore access to my previously earned Microsoft for Startups Azure credits?

Impact:

I cannot view or use my previously granted Azure startup credits, and the system appears to be treating my existing verified startup account as a new application.

Please check:

Whether my Microsoft for Startups verification is still active

Whether my Azure credits are linked to the correct Microsoft account / tenant

Whether there is a duplicate startup application causing the BadRequest (Conflict) error

Whether my LinkedIn verification is already associated with another profile or application

How I can regain access to the previously earned credits without submitting a new application

I can provide screenshots of the redirect flow, the LinkedIn verification step, and the error message if needed.

Thank you.

Azure | Azure Startups
Azure | Azure Startups

Startups: Companies that are in their initial stages of business and typically developing a business model and seeking financing.

0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-06-01T20:50:18.8533333+00:00

    The behavior described (being sent back through the “Apply for Microsoft for Startups” flow and seeing a BadRequest (Conflict) error) cannot be fully diagnosed or fixed self-service and requires program support to review the specific startup profile, account, and credit linkage.

    Based on the available information, the next steps are:

    1. Use the correct portal for the program version
      • If the startup joined Microsoft for Startups before May 29, 2026, manage the membership and benefits (including Azure credits) via the Microsoft for Startups Portal.
      • If the startup joined after May 29, 2026, the primary experience is via the Azure Portal program page documented for Microsoft for Startups.
    2. Submit a support request to Microsoft for Startups Because this issue involves:
      • A previously verified startup
      • Existing Azure credits that are no longer visible
      • A BadRequest (Conflict) error during the application/verification flow the program team must check the backend records (verification status, duplicate applications, LinkedIn linkage, and credit assignment) and correct any conflicts.
      To contact support:
      • If using the Microsoft for Startups Portal (for earlier cohorts):
        1. Sign in to the Microsoft for Startups Portal.
        2. Select the “?” icon in the top-right corner.
        3. Select “Submit a Support Ticket” and attach screenshots of:
          • The redirect to the “Apply for Microsoft for Startups” screen
          • The LinkedIn verification step
          • The BadRequest (Conflict) error details
      • If using the Azure Portal experience (for newer cohorts):
        • Use the Microsoft for Startups program page in the Azure Portal and submit a support request from there, as documented for the post–May 29, 2026 experience.
    3. Ask support to verify and correct the following In the support ticket, explicitly request that the team:
      • Confirm whether the existing Microsoft for Startups verification is still active.
      • Confirm which Microsoft account / tenant the startup’s Azure credits are currently linked to.
      • Check for and resolve any duplicate startup applications or profile conflicts that could cause the BadRequest (Conflict) error.
      • Verify whether the LinkedIn verification is already associated with another startup profile or application and, if so, align it with the correct one.
      • Restore access to the previously granted Azure credits without requiring a new application, if the startup is still eligible.
    4. Verify credits once support has corrected the profile After support resolves the conflict and confirms access:
      • Sign in to the Azure portal and verify credits under Cost Management > Billing > Payment methods, as documented for Azure credit activation.
      • Ensure the correct subscription (the one with startup credits) is visible and used for workloads.

    If the credits were never activated or expired (for example, not activated within 90 days of accepting the program agreement), support can also confirm whether the offer is still valid or if a reapplication is required.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.