Microsoft for Startups: "Verify with LinkedIn" returns HTTP 400 and no application is ever created

Armore Azure Admin 0 Reputation points
2026-11-20T21:33:09.93+00:00

We're a newly incorporated startup (India, private limited) trying to join Microsoft for Startups through the new Azure portal experience. We can't get past verification, and there's no support channel available before enrolment.

Steps: (1) Sign in to portal.azure.com with a work account in our own tenant. (2) Open "Apply for Microsoft for Startups" and click "Continue without a code" (no investor referral code). The page goes straight to the "Build your startup" preview dashboard; network capture shows no request to the startups backend at this step. (3) On the dashboard, click "Verify with LinkedIn" on the "Unlock $200 in Azure credits" tile.

Result, reproduced 5 times between 19 and 21 Nov 2026, including after an active Azure subscription was added to the tenant: startupsweb.production.portalrp.azure.com/api/auth/linkedin/auth-url (api-version 2026-07-01-preview) returns 400; /api/user (api-version 2026-03-01-preview) returns 404; /api/application/current (api-version 2026-03-01-preview) returns 404. No request is ever made to linkedin.com.

Also tried: portal.startups.microsoft.com "Sign in with LinkedIn" completes the LinkedIn OAuth consent, but the portal returns 401 for /api/user/me and redirects back to the same Azure dashboard. A personal Microsoft account on the same domain is redirected to the Azure home page, and no Microsoft for Startups page appears at all. Azure Help + support has no Microsoft for Startups service, and the program-support entry ("Your Microsoft Team", "Get program support") only exists after enrolment.

Question: how can a new applicant complete verification or create an application when the auth-url call returns 400? Is there a support route for applicants who are not yet enrolled?

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-11-20T21:34:16.5166667+00:00

    The supported resolution is to restart the application with a new personal Microsoft account that has never been associated with Azure, because the work/Entra account used here is not supported for Microsoft for Startups enrollment.

    Create the application with an eligible account

    1. Create a new personal Microsoft account
      • Use a new Outlook.com/Hotmail.com address, or a Gmail address registered as a Microsoft account.
      • Do not use the company’s Microsoft Entra work account.
      • Avoid a company-domain address if that domain is managed by the organization.
      • The account must not have been used for an Azure subscription, Azure Free Trial, Azure for Students, another sponsorship, or a previous Startups application.
      Microsoft explicitly states that work or school accounts are unsupported and can produce eligibility errors during application or credit activation. It also requires a new personal account with no previous Azure association.^1^
    2. Start in a clean browser session
      • Sign out of both Microsoft and LinkedIn.
      • Open an InPrivate/Incognito window to prevent the work account from being selected silently.
      • Start from the Microsoft for Startups landing page and select Get started now.
      • Sign in with the new personal Microsoft account.
    3. Select Continue without a code
      • Reaching the preview Build your startup dashboard at this point is expected; the no-code path does not first present the longer investor application form.
      • Select Verify with LinkedIn and use the founder’s personal LinkedIn profile.
      • Successful verification should continue to the three-step Azure account creation flow. LinkedIn verification must occur before that Azure account is created.^2^
    4. Complete the new Azure account setup
      • Enter the country/region matching the billing address.
      • Complete profile, address, and payment-card verification.
      • Do not attempt to attach the existing tenant subscription as a substitute for this flow. The Startups process creates the eligible Azure account after LinkedIn verification.^2^

    The personal account already tested on the company domain is not a conclusive test if that domain is organizationally managed or if the account has prior Azure history. Adding an active Azure subscription to the original tenant does not satisfy the documented prerequisite and can make that identity ineligible for the “new Azure account” offer.

    If the new eligible account still returns auth-url 400

    At that point, capture one failing attempt and request escalation as a portal/onboarding failure. Include:

    • UTC timestamp and country/region
    • Browser and InPrivate status
    • Confirmation that the Microsoft account is personal, newly created, and has no Azure history
    • HTTP status and full request path for:
      • api/auth/linkedin/auth-url
      • api/user
      • api/application/current
    • Correlation/request IDs from response headers, if present
    • HAR file and screenshots, with tokens, cookies, and personal data removed
    • Statement that no request reaches LinkedIn

    The auth-url failure occurs before LinkedIn redirection. In the documented LinkedIn integration, the application must obtain a dynamic verification URL and redirect the member to it; without that URL, the LinkedIn verification flow cannot start.^3^

    Support before enrollment

    Microsoft documents Microsoft for Startups Program Support as the owner for onboarding, portal, benefit-activation, and verification issues. However, its published contact procedure requires opening Azure portal → Microsoft for Startups Program Overview → Your Microsoft Team → Get program support.^4^

    The public documentation does not identify a separate applicant-only ticket form when that control is unavailable. In that situation:

    1. Use Microsoft’s general Contact Support flow, enter “Microsoft for Startups application portal,” select Get Help, and then Contact Support when offered.^5^
    2. State explicitly that this is a pre-enrollment Startups portal/onboarding incident, not an Azure subscription runtime or billing problem.
    3. Provide the diagnostic package above and request routing to Microsoft for Startups Program Support.
    4. Keep the Microsoft Q&A thread open with the sanitized request IDs if support cannot route the case; the same auth-url 400 and /api/user 404 pattern has been reported in the current Startups experience, although that report does not yet contain an accepted workaround.^6^

    There is no documented client-side method to create /api/application/current manually or bypass the required LinkedIn step.


    References

    1. Microsoft for Startups – Frequently asked questions
    2. Overview of the Microsoft for Startups application process
    3. Verification URL - LinkedIn | Microsoft Learn
    4. Microsoft for Startups Program Support | Microsoft Learn
    5. Troubleshoot Microsoft verification code issues | Microsoft Support
    6. Microsoft for Startups LinkedIn verification does not redirect. - Microsoft Q&A
    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.