GitHub Enterprise Billing Blocked: "No Subscriptions Found" Error Impacts Development Analytics

GitHub Enterprise Billing Blocked: Widespread "No Subscriptions Found" Error Plagues Azure Integrations

A critical and widespread issue has emerged, preventing GitHub Enterprise Cloud users from successfully linking their Azure subscriptions for metered billing. Despite exhaustive verification of Azure-side configurations, users are consistently encountering the error message: "No subscriptions found. Please make sure you have owner permissions for the subscription you are trying to select." This problem significantly impacts organizations' ability to manage cloud spend and gather accurate development analytics related to their GitHub Enterprise usage.

The Problem: Verified Azure, Empty GitHub Subscription List

The issue, initially highlighted by FelixKotikYT in a GitHub Community discussion, details a meticulous troubleshooting process. The user, attempting to connect an Azure Pay-As-You-Go subscription to a GitHub Enterprise Cloud trial account, confirmed every documented prerequisite on the Azure side:

• User held Owner permissions on the Azure subscription (verified via IAM).
• Microsoft.SaaS and Microsoft.MarketplaceOrdering resource providers were registered.
• The Azure subscription was Enabled and Active, with no spending limits.
• The GitHub SPV (Subscription Permission Validation) app was present in Entra ID as an Enterprise Application.
• Admin consent was granted for the SPV app (user_impersonation on ARM), with successful sign-in logs (error code 0).
• Multiple Azure subscriptions (with and without free tier promotions) were tested, yielding identical results.
• Azure Policies and Conditional Access were verified not to be blocking the SPV app.

Despite these comprehensive checks, the OAuth flow would successfully redirect to Microsoft login, the user would authenticate, and GitHub would redirect back to an empty subscription selection page. The core problem appears to be GitHub's inability to enumerate available Azure subscriptions, even when all permissions and configurations are correctly set on the Azure side.

A Widespread and Persistent Challenge

The discussion quickly garnered significant attention, with dozens of users reporting the exact same problem. This indicates a systemic issue rather than isolated configuration errors. Key observations from the community further illuminate the nature of the bug:

• New vs. Existing Connections: Several users noted that older Azure subscriptions, which were successfully connected to GitHub billing before this issue arose (e.g., in January 2026), continue to function and bill correctly. However, attempts to connect new subscriptions or even re-enumerate previously connected ones result in the "No subscriptions found" error. This suggests a potential regression in GitHub's subscription enumeration API.
• Impact on Different Subscription Types: The problem affects various Azure subscription types, including Pay-As-You-Go and Sponsorship subscriptions.
• Lack of Official Solution: As of the discussion's activity, neither GitHub nor Microsoft support had provided a definitive solution or workaround, leaving many organizations in limbo. Users reported opening tickets with both platforms, often being redirected between them.

Implications for Software Metrics and Resource Management

This connectivity breakdown has significant implications for organizations relying on GitHub Enterprise Cloud. Without the ability to link Azure subscriptions for metered billing, businesses face challenges in:

• Cost Management: Inability to accurately track and attribute GitHub Enterprise usage costs, hindering budget planning and financial development analytics.
• Resource Provisioning: Delays or blocks in provisioning services that rely on metered billing, potentially impacting project timelines and team productivity.
• Operational Transparency: Reduced visibility into the operational software metrics associated with GitHub Enterprise, making it harder to optimize cloud resource consumption.

While no immediate solution emerged from the community discussion, the collective reporting underscores the urgency for GitHub and Microsoft to address this integration bug. Users experiencing this issue are encouraged to contribute to relevant support tickets and community discussions to help expedite a resolution.