Clarify 20-character limit for assignable permission set names in object-name guidance

[mundanebcdev]

Affected guidance

microsoft/knowledge/style/object-name-30-char-limit.md

Problem

The article includes permission sets in its general 30-character object-name limit. Its Best Practice section also recommends a descriptive name in the 20-26-character range, with additional space reserved for an app prefix.

There is an exception for assignable permission sets. The AL0305 diagnostic remarks on Microsoft Learn state:

For permission sets specifically, the diagnostic will also be triggered, if a permission set with the Assignable property set to true exceeds 20 characters.

The documented limits for permission set names are therefore:

Permission set configuration	Maximum name length
Assignable = true	20 characters
Assignable = false	30 characters

Following the current guidance can produce an assignable permission set name of 21-30 characters that appears compliant with the article but triggers compiler diagnostic AL0305.

Suggested correction

• Qualify the general 30-character rule with the 20-character exception for permission sets where Assignable = true.
• Adjust the Best Practice section so the complete assignable permission set name, including any prefix or suffix, fits within 20 characters. The 20-26-character descriptive-name recommendation should not apply to these objects.
• Link to the AL0305 remarks and clarify that exceeding this limit is a compiler error, not only a publish-time validation concern.

The general 30-character guidance can remain, provided this exception is explicit.

[JesperSchulz]

Thanks for documenting the assignable permission-set exception so clearly and for linking the AL0305 guidance. If you believe this nuance is missing from the current article, please feel very welcome to open a focused PR with the proposed wording. There is no need to file an issue first; a PR is the quickest path, and we would be happy to review it.