Document user license requirements for @-mentions in SPE docs #10301
Conversation
|
Learn Build status updates of commit 8eb2b24: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 97dc791: ✅ Validation status: passed
For more details, please refer to the build report. |
| > [!NOTE] | ||
| > Mentions require target users to [have an M365 license assigned to them](../auth.md#mention-users-in-office-documents). | ||
| > | ||
| > Mentions are restricted to people inside the consuming tenant's organization. Mentions excludes Guests and users from other tenants in a Multi-Tenant setting. |
There was a problem hiding this comment.
This was copied directly from the @-mentions documentation, but having "Guests" (upper-case G) and "Multi-Tenant" (upper-case M and T) looks a bit off. I'll leave this up for reviewers, I'd change all of those to lower-case.
There was a problem hiding this comment.
I suggest, not just for this, but for all content updates, is to run this through Acrolinx. You can learn more about this from the MSDocs/MSLearn MSFT-internal site.
In a nutshell, Acrolinx is like Grammarly, but for Microsoft's style guide. MSDocs uses it, and all content published to MSLearn's training section (modules, labs, etc), must have a score of 80+ to get published. It finds things like these.
In this case, it doesn't flag the uppercase "Guest", but the correct use of the other is "multitenant" (one word, all lowercase). I'll submit my changes from running this page through Acrolinx
|
Learn Build status updates of commit 6c6fb8b: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 6dd3dd4: ✅ Validation status: passed
For more details, please refer to the build report. |
andrewconnell
added
pr:ready-to-merge
Category
What's in this Pull Request?
Documents user license requirements for @mentions in Office documents for SPE.