Startups: Companies that are in their initial stages of business and typically developing a business model and seeking financing.
The email means the startup has already been enrolled in Microsoft for Startups and the Azure credits/benefits have been issued, but access to those benefits is controlled separately from the program enrollment.
For Microsoft for Startups credits and benefits, two things are distinct:
- Program enrollment and benefits being granted to the startup
- Access for individual team members to the Azure subscription and resources where those credits were applied
In this situation, the startup is already accepted and has credits, but the individual account isn’t yet connected to the subscription or tenant where those credits live.
To resolve this:
- Identify who activated the credits
- Typically the founder or whoever received and redeemed the original Microsoft for Startups credit offer email.
- That person’s Microsoft Account (for example, a personal MSA such as
******@outlook.comor******@gmail.com) usually owns the subscription where the credits were applied.
- Have that person verify the Azure setup
- They should sign in to the Azure portal with the account that redeemed the credits and confirm:
- Which subscription has the Microsoft for Startups credits applied.
- Which Microsoft Entra ID tenant (directory) is associated with that subscription.
- They should sign in to the Azure portal with the account that redeemed the credits and confirm:
- Have them grant access to the subscription
- As long as they are an Owner/Admin on the subscription, they must explicitly add the user as a role assignment on that subscription using Azure RBAC.
- They should follow the documented steps in “Steps to assign an Azure role – Azure RBAC” to assign at least the Reader, Contributor, or Owner role on the startup’s subscription to the user account.
- Until this role assignment is done, the user will see messages like “You’re not currently assigned to your startup’s Azure subscription” and won’t see or use the credits.
- Ensure the company tenant is set up correctly (if not already)
- Credits are initially tied to an individual’s Microsoft Account, but the recommended setup is to:
- Establish a company-backed Microsoft Entra ID tenant with a custom domain (for example,
@contoso.com). - Make sure the person who activated the credits has the correct admin permissions in that tenant.
- Add other team members to that tenant and grant them access to the subscription.
- Establish a company-backed Microsoft Entra ID tenant with a custom domain (for example,
- Credits are initially tied to an individual’s Microsoft Account, but the recommended setup is to:
If, after being added to the subscription via Azure RBAC, the user still doesn’t see credits, the owner should:
- Confirm that the credits were actually redeemed and applied to the correct subscription in the Microsoft for Startups Portal.
- Verify that the user is signing in with the same identity (work account vs personal MSA) that was granted access.
Program acceptance alone doesn’t automatically expose credits to every team member; subscription access must be explicitly granted by the person who activated the credits.
References: