- Notifications
You must be signed in to change notification settings - Fork62.5k
Add workaround for when organization’s active sponsorships are canceled after joining an enterprise with Azure billing#39243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out thecontributing guidelines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Pull Request Overview
This PR fixes linting issues with headings and improves documentation for organizations being added to enterprises with Azure billing. The changes primarily address GitHub Sponsors compatibility issues when organizations join enterprises using Azure metered billing.
- Adds comprehensive guidance for handling GitHub Sponsors cancellations under Azure billing
- Provides a workaround using "shell" organizations for continued sponsorship management
- Fixes punctuation formatting in step-by-step instructions
Comments suppressed due to low confidence (1)
content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md:74
- This line uses 'GitHub Sponsors' instead of the defined variable. According to the content guidelines, you should use
{% data variables.product.prodname_sponsors %}instead of hardcoded text for product names.
To continue using GitHub Sponsors, create a new, separate "shell" organization that is not linked to your enterprise account or Azure billing. You can then use this shell organization to manage sponsorships independently of your enterprise’s billing setup....itories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
...itories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
github-actionsbot commentedJul 9, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key:fpt: Free, Pro, Team;ghec: GitHub Enterprise Cloud;ghes: GitHub Enterprise Server 🤖 This comment isautomatically generated. |
| @@ -76,9 +91,9 @@ During a trial of {% data variables.product.prodname_ghe_cloud %}, you can creat | |||
| 1. In the left sidebar, click **Organizations**. | |||
| {%- endif %} | |||
| 1. Above the list of organizations, click **New organization**. | |||
| 1. Under "Organization name", type a name for your organization. | |||
| 1. Under "Organization name," type a name for your organization. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Place comma inside the quotation marks
https://owl.purdue.edu/owl/general_writing/punctuation/quotation_marks/more_quotation_mark_rules.html
...itories/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
…nizations-in-your-enterprise/adding-organizations-to-your-enterprise.mdCo-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com>
Uh oh!
There was an error while loading.Please reload this page.
Why:
Closeshttps://github.com/github/sponsors/issues/6228
What's being changed (if available, include any code snippets, screenshots, or gifs):
This PR updates the documentation for adding an existing organization to an enterprise, specifically addressing the impact on GitHub Sponsors when the enterprise uses Azure billing. It adds clear guidance for organizations whose sponsorships are canceled during this process and provides a workaround so they can continue to use GitHub Sponsors.
Problem
When an existing organization is added to an enterprise account with Azure metered billing, all active GitHub Sponsors sponsorships are canceled. Organizations are unable to reactivate sponsorships or add a payment method due to enterprise billing restrictions, and current documentation does not provide clear next steps for affected organizations.
Solution
This PR adds a new subsection to the “Changes when adding an existing organization” section. It explains why sponsorships are canceled, clarifies that reactivation is not possible under Azure billing, and recommends creating a standalone "shell" organization to manage sponsorships outside the enterprise billing structure.
Check off the following:
Here’s a draft for your pull request description:
Checklist