Azure subscription not found when connecting to GitHub Enterprise Cloud — all Azure-side configs verified

[FelixKotikYT]

🏷️ Discussion Type

Bug

Body

A friend of mine is trying to connect an Azure subscription to their GitHub Enterprise Cloud account for metered billing, but keeps getting "No subscriptions found. Please make sure you have owner permissions for the subscription you are trying to select."

We've exhaustively verified every Azure-side configuration and can't figure out what's wrong. Hoping someone has seen this before.

Environment

• GitHub Enterprise Cloud (created as a trial, ~30 days in)
• Azure Pay-As-You-Go subscription (Enabled, no spending limit)
• Using the "Pay with Azure" tab under Enterprise → Billing → Payment Information

What was verified on the Azure side

Check	Status
User is Owner on the Azure subscription	✅ Confirmed via IAM
Microsoft.SaaS resource provider registered	✅ Registered
Microsoft.MarketplaceOrdering resource provider registered	✅ Registered
Subscription is Enabled and Active	✅ Pay-As-You-Go, no spending limit
GitHub SPV app (Subscription Permission Validation) exists in Entra ID	✅ Present as Enterprise Application
Admin consent granted for SPV app (user_impersonation on ARM)	✅ AllPrincipals consent
SPV app sign-in logs	✅ All sign-ins show Success (error code 0)
Tried multiple Azure subscriptions	✅ Same result on 2 different subscriptions
Tried subscription with and without free tier promotion	✅ No difference

OAuth flow observations

• The OAuth redirect to Microsoft login works fine
• User authenticates successfully
• GitHub redirects back to the subscription selection page
• The subscription list is empty despite the user being Owner on active subscriptions
• The SPV app's sign-in logs in Entra ID show successful authentication from GitHub's server IP

What was tried

1. Created a brand new Azure subscription specifically for this — same result
2. Registered Microsoft.SaaS provider manually — no change
3. Granted admin consent for the SPV enterprise app — no change
4. Tried with different Azure users (all Owners on the subscription) — same result
5. Cleared browser cache, tried different browsers — same result
6. Verified no Azure Policies or Conditional Access blocking the SPV app

Questions

1. Has anyone else encountered "No subscriptions found" with all Azure configurations verified correct?
2. Is there a known issue with connecting Azure subscriptions to Enterprise accounts that are still on a trial?
3. Is there any additional Azure-side configuration not mentioned in the official docs that might be required?
4. Could the Azure tenant or subscription region matter?

Any help would be greatly appreciated. We've spent days on this.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[AI-summain]

Just here to report that we have exactly the same problem. There should be no issue in Azure side. I'm owner of multiple subscriptions in our tenant but none are available to select as billing subscription

[AI-summain]

It's also nice to see that we still get billed for our copilot business seats that we have in our organization, even though we can't use them after upgrading to enterprise 👍

[ouederniAmine]

Did you get a response from github?

[AI-summain]

No response to support ticket yet. Ticket is one week old now.

[stijndevoogd]

We are also facing this issue.

[SathiraDM]

Same here, I've tried multiple subscription connections but it always says "No subscriptions found. Please make sure you have owner permissions for the subscription you are trying to select."

[esavini]

same issue, I am global administrator on azure and I cannot connect any subscription

[esavini]

I have tried again, no way to get it working...

[esavini]

From the support:

Hi there,

Sorry for the delay in getting back to you; We've been experiencing a high volume of support requests, and we haven't been able to respond to some questions as quickly as we would usually.

We've recently made some changes that mean fewer types of Azure subscription can now be linked to a GitHub account.

If you've met the prerequisites in this guide and still don't see your subscription listed, it likely means that your Azure subscription type is not eligible to be connected to GitHub. I’m sorry for any frustration this causes.

Additional details will be available in our documentation soon.

Kind regards,

GitHub Support

[VAIBHAVSING]

i am also facing this issue

[Loptim]

same issue

[Tim-CoditBE]

I'm having this exact same issue. Already opened a ticket at Github support.
I can see older subscriptions, but not the newly created one that we need to use.

[moatezouarteni01-gif]

did anyone get an update??

[Tim-CoditBE]

I've created a ticket at Microsoft via Partner support. I'll update here if I have news.

[VAIBHAVSING]

i have too but they are only throwing dirt on github haha

[Tim-CoditBE]

:)

[moatezouarteni01-gif]

:)

idk how a billion dollar company have such bad support

[mhawley69]

Having the exact same issue...

[biboyursua-pixel]

Hi help me

[VAIBHAVSING]

I opened a qna at Microsoft discussion hope we get resolution

https://learn.microsoft.com/en-us/answers/questions/5868139/github-metered-billing-via-azure-problem?orderby=newest&page=1#answers

[mhawley69]

Thanks!

[biboyursua-pixel]

Hi

[frankinfocures]

upvote. Having the same issue.

[marwenbk]

same issue here

[arf-kochoai]

Just to add another one to the list, exact same scenario here, exact same steps, exact same error.

[MartinSaalmann]

If you raise a ticket, Github no tells you that Azure Sponsorships are not supported and that you have to raise a ticket with microsoft.

"Based on the GitHub billing documentation, GitHub relies on Azure’s Subscription Permission Validation (SPV) app to list eligible subscriptions in your tenant. Azure Sponsorship / legacy Azure subscriptions are not supported for GitHub billing, so they will not appear in the subscription picker—even if you are the owner and activation succeeded in Azure.

What this means in practice:

GitHub Copilot billed through Azure requires a regular Azure subscription that supports metered billing.
Azure Sponsorship (credit-based or legacy) subscriptions don’t qualify, so GitHub cannot attach Copilot charges to them.
This behavior is expected and not something you can fix through configuration changes.

If your Microsoft sponsorship was intended to cover Copilot usage, you’ll need to raise this with Microsoft, as GitHub can’t enable Copilot billing on unsupported subscription types."

[hung-doan]

I'm not sure about that as the standard PAYG subscription doesn’t work either.

[esavini]

I have received a reply from GitHub, these subscription are not supported.

Quota ID	Offer number(s)
FreeTrial_2014-09-01	MS-AZR-0044P
AzureForStudents_2018-01-01	MS-AZR-0170P
DreamSpark_2015-02-01	MS-AZR-0144P
AzurePass_2014-09-01	MS-AZR-0120P, MS-AZR-0122P–MS-AZR-0125P, MS-AZR-0128P–MS-AZR-0130P
PayAsYouGo_2014-09-01	MS-AZR-0017G
Sponsored_2016-01-01	MS-AZR-0036P

https://docs.github.com/en/enterprise-cloud@latest/billing/reference/supported-payment-methods#unsupported-azure-subscription-types

[Tim-CoditBE]

Weird because MS-AZR-0036P is this benefit...

[esavini]

I have requested in the ticket what subscriptions are allowed, at the moment I think no one is enabled, even the Pay as you Go is not enabled.

[nico-mojo]

Hello,
here are the offers you can link subscriptions on : https://azure.microsoft.com/en-us/support/legal/offer-details

I got 0017G and 0036P subscriptions... The pay-as-you-go should be 0003P but they linked it to 0017G which is Azure Plan

[frankinfocures]

They updated the article and don't have that table anymore. I just think its chaos over at GitHub and are purposely not getting new users. They don't list what subscriptions are accepted and are not communicating. Their support and on-boarding staff aren't any help sending the same bs articles. This is the single worst on-boarding to a enterprise product I have ever witnessed.

[nico-mojo]

there were some changes, today my subscription type MS-AZR-0036P (Azure sponsorship trough partner portal) is visible and can now be linked (I just did it)

[Tim-CoditBE]

I've opened a ticket with Microsoft Partner. We are losing $60k in Azure credits because of this change :)

[ngcodingtn-create]

pls update us if there is anything

[uzobizu]

same here, this is so annoying. hopefully you get a response

[noonessh]

it seems someone considered MS-AZR-0036P to be obsolete/old ( Sponsored_2016-01-01 ) but it's not!!!

[ans-ng]

100% agree it's not obsolete, my own Partner Sponsorship credits for GitHub were provisioned as 0036P on 6th May and are now unavailable to use in GitHub.

My understanding is Microsoft are changing how Partner Sponsorship credits are being applied from subscriptions to billing profiles, but this has fully rolled out yet which I think might be related to this problem.

[tomsworldbe]

This is very bad news :(
We were as well planning to use our partner resources for this - so those are unusable ...

[rapavaricio]

still no luck.. same problem. all requirements are check on the setup.

[hung-doan]

FYI I can now see my MS-AZR-0036P subscription now from Github now.
p/s ensuring the "GitHub Subscription Permission Validation" application has been installed to your Entra Id, and your administrator has granted the admin consent to that application.

[rapavaricio]

it already is ont my side.. how did you do it.

[hung-doan]

I did nothing, it seems Github fixed something though?

[noonessh]

I also confirm that MS-AZR-0036P is now visible in Payment information of GitHub Enterprise configuration, without any extra actions from my side. Thank you!

[ans-ng]

Also working for me with no changes on my side, I have successfully added my MS-AZR-0036P subscription with Azure Sponsorship Credits. Got there in the end GitHub :-)

[Tim-CoditBE]

Also fixed here. We can add our Partner subscriptions again as billing method.
Still baffled how they support Enterprises as such a big company.

[rapavaricio]

oh man.. what did i miss here?? T_T all my setup is good.. oh man.. its really frustrating.. subscriptions not showing under my tenant.. but logs show it is accessed.

[rapavaricio]

ooh it seems my sub is PayAsYouGo_2014-09-01 .. damn

[raslavs]

Did the issue get resolved? We received the exact same partner benefit from Microsoft, but the subscription is showing as unsupported in GitHub.A ticket was opened with Microsoft Partner Support, and they replied that everything is fine on their side. I also opened a ticket with GitHub Copilot Support, but I still haven’t received a response.

[ans-ng]

This was fixed by GitHub/Microsoft on the 14th May for our Enterprise, I have to assign a new sponsorship credit in the next couple of days so will update if it's become an issue again.

[Jamonygr]

Given everything you already verified on the Azure side, I would look at GitHub billing eligibility and tenant/account matching next.

A few things can cause this even when the user is Owner on an active subscription:

1. The GitHub enterprise account is not eligible or enabled for Azure metered billing yet.
2. The signed-in Microsoft account is not in the same Entra tenant context GitHub expects during the payment connection flow.
3. The Azure subscription type is not accepted for this GitHub billing path, even though it is active.
4. There is an enterprise billing state, trial state, unpaid balance, or contract condition preventing the switch.
5. GitHub's subscription validation app succeeds at sign-in but still filters the subscription out later.

Because the SPV sign-in succeeds, this does not look like a basic OAuth/admin-consent issue. I would send GitHub Support the enterprise slug, Azure tenant ID, subscription ID, timestamped SPV sign-in logs, and screenshots of the empty selector. This feels like a backend eligibility/filtering issue on the GitHub billing side.

[Jamonygr]

This really does sound like the Azure side is probably correct and the issue may be on GitHub’s billing eligibility or subscription-enumeration side. If multiple subscription owners, multiple active subscriptions, registered providers, and successful SPV sign-ins all produce an empty list, I’d ask GitHub Support specifically to verify whether the enterprise account is enabled for Azure metered billing and whether trial status affects subscription selection. I’d include the tenant ID, subscription IDs, enterprise slug, screenshots, and the successful Entra sign-in logs so support does not send you back through the same Azure checks again.