Skip to content
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

Update admin note in manage-office-scripts-settings.md #13705

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

alison-mk
Copy link
Contributor

No description provided.

Copy link
Contributor

Learn Build status updates of commit d82e2a7:

✅ Validation status: passed

File Status Preview URL Details
microsoft-365/admin/manage/manage-office-scripts-settings.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

Removed mention of "Global admin" (per security recommendations) and reworded to include the phrase "at least".
Copy link
Contributor

Learn Build status updates of commit 5f9e6ba:

✅ Validation status: passed

File Status Preview URL Details
microsoft-365/admin/manage/manage-office-scripts-settings.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@SKjerland
Copy link
Contributor

@alison-mk - I made a minor edit to the sentence to follow our security recommendations around the use of "Global Admin" in our help articles. Also, I noticed you updated the ms.date metadata field. This field should only be updated if you reviewed the entire article and confirmed that the content is correct and up to date. Did you do that? I just want to make sure the article is actually up to date and doesn't require a freshness review from a SME. Thanks!

@SKjerland SKjerland merged commit c4cd608 into MicrosoftDocs:public Jan 10, 2025
6 checks passed
@alison-mk alison-mk deleted the patch-3 branch January 14, 2025 01:03
@alison-mk
Copy link
Contributor Author

@SKjerland Thanks for the feedback and merging the PR! Based on your criteria, I shouldn't have updated the ms.date field. My apologies! Should I change it back?

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.

2 participants