Skip to content

Adding documentation support says should be in this article? #1708

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jonwbstr
Copy link

@jonwbstr jonwbstr commented Aug 8, 2025

As a partner I opened ticket 2502260010001012 back in February of this year. According to the response I received on that ticket today,

The recommended approach to workaround [Accounts using PIM not receiving email] is to have enabled admin accounts for "Break Glass" scenarios, assign an email account and then forward all notifications to a DL. We have a well documented procedure to configure it and it will allow you to get the notifications:Manage emergency access admin accounts - Microsoft Entra ID | Microsoft Learn.

This is a similar approach to the one I believe you’re currently applying as per our last conversation.

Since this article doesn't even give a gist of how to do what they indicate is well documented, I propose the following changes so that supports assessment of this article is at least sort of correct. Feel free to improve upon this guidance. Creating step by step guidance on how to make the break glass account mail enabled and setup the forward is not a high priority to me considering support believes the article already has that information. Hopefully someone on your team is already working on this!

This is the article where I was expecting to find the guidance support says exists in this article.
https://learn.microsoft.com/en-us/microsoft-365/business-premium/m365bp-protect-admin-accounts?view=o365-worldwide#create-a-user-account-for-yourself

Hope this helps!
-jon

According to ticket 2502260010001012 this article describes the workaround of using the break glass account to forward admin email notifications to admin accounts configured with PIM, or following Microsoft's guidance to have separate unlicensed global admin accounts and licensed mail-enabled users with no admin roles found in the following article

https://learn.microsoft.com/en-us/microsoft-365/business-premium/m365bp-protect-admin-accounts?view=o365-worldwide#create-a-user-account-for-yourself
Copy link
Contributor

@jonwbstr : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 652e753:

✅ Validation status: passed

File Status Preview URL Details
docs/identity/role-based-access-control/security-emergency-access.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@barclayn

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants