Startups: Companies that are in their initial stages of business and typically developing a business model and seeking financing.
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:
- 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.
- 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.
- If using the Microsoft for Startups Portal (for earlier cohorts):
- Sign in to the Microsoft for Startups Portal.
- Select the “?” icon in the top-right corner.
- 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.
- 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.
- 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: