Willkg: truncating content as we transition ownership from IT to CloudEng

2026-10-07T21:23:48Z

truncating content as we transition ownership from IT to CloudEng

← Older revision		Revision as of 21:23, 7 October 2026
Line 1:		Line 1:
	~~Requiring 2FA is an easy way~~ to ~~improve the security of your organization~~. ~~And, it is also good for your contributors~~. ~~Everyone benefits from utilizing 2FA~~. ~~(There are a few cases where 2FA may not be practical for all contributors~~. Please reach out ~~if you believe you have such a case.) In addition, requiring 2FA is a~~ [https://~~mana~~.mozilla.org/~~wiki/display/POLICIES/Standard%3A+GitHub+repositories+and+organizations requirement~~] for ~~Mozilla managed GitHub organizations~~.		'''2026-10-07: GitHub Enterprise ownership has been transitioned from IT to CloudEng.''' Customer documentation has been moved to [https://mozilla-hub.atlassian.net/wiki/spaces/GHE/pages/3087892663/Getting+help+with+GitHub Getting help with GitHub] in Confluence. Please update any links to this page accordingly. If you are an external contributor, please reach out to your sponsor in the appropriate [https://chat.mozilla.org/ Matrix channel] for support.

	~~GitHub provides good instructions on [~~https://~~docs.github.com/en/github/setting~~-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization enabling 2FA] for your organization, including discussion of the impact it will have on current contributors. Here are some things to highlight:		This content has been moved to: https://mozilla-hub.atlassian.net/wiki/spaces/GHE/pages/3144351864/Organizations#Two-factor-authentication

	* Do check to see who will be removed from the organization if you enable 2FA.
	* Do remember that any automation set up by a non-2FA login will also be disabled when they are removed from the organization.
	* Set up a private team to communicate with organization members who do not have 2FA, as you may not have emails for them. ~~(Private, so you don’t advertise their accounts do not have 2FA enabled~~.)
	* Do give your non-2FA contributors a reasonable amount of time to enable 2FA.

	~~When you are ready to require 2FA for your organization:~~

	* If you can, notify everyone of the upcoming change, and give the date.
	** Include the link to [https://~~docs.github.com~~/en/~~github~~/~~authenticating-to-github~~/~~securing-your-account-with-two~~-factor-authentication~~-2fa setting up 2FA on a user account] instructions to assist individuals.~~
	* Let folks know that some automation might break.
	* Change your organization settings to require 2FA.
	* Embrace the future!

	~~If you do have questions or concerns, please chat with us in the [https://chat.mozilla.org/#/room/#github-admin:mozilla.org GitHub-Admin] channel on Matrix.~~

Hwine: initial post - to be referenced in an email

2021-01-21T21:47:53Z

initial post - to be referenced in an email

New page

Requiring 2FA is an easy way to improve the security of your organization. And, it is also good for your contributors. Everyone benefits from utilizing 2FA. (There are a few cases where 2FA may not be practical for all contributors. Please reach out if you believe you have such a case.) In addition, requiring 2FA is a [https://mana.mozilla.org/wiki/display/POLICIES/Standard%3A+GitHub+repositories+and+organizations requirement] for Mozilla managed GitHub organizations.

GitHub provides good instructions on [https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization enabling 2FA] for your organization, including discussion of the impact it will have on current contributors. Here are some things to highlight:

* Do check to see who will be removed from the organization if you enable 2FA.
* Do remember that any automation set up by a non-2FA login will also be disabled when they are removed from the organization.
* Set up a private team to communicate with organization members who do not have 2FA, as you may not have emails for them. (Private, so you don’t advertise their accounts do not have 2FA enabled.)
* Do give your non-2FA contributors a reasonable amount of time to enable 2FA.

When you are ready to require 2FA for your organization:

* If you can, notify everyone of the upcoming change, and give the date.
** Include the link to [https://docs.github.com/en/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa setting up 2FA on a user account] instructions to assist individuals.
* Let folks know that some automation might break.
* Change your organization settings to require 2FA.
* Embrace the future!

If you do have questions or concerns, please chat with us in the [https://chat.mozilla.org/#/room/#github-admin:mozilla.org GitHub-Admin] channel on Matrix.

GitHub/Converting to a "2FA required policy" - Revision history

Willkg: truncating content as we transition ownership from IT to CloudEng

Hwine: initial post - to be referenced in an email