Sunday, October 2, 2022
HomePowershellOutline Groups naming insurance policies - Energetic Listing FAQ

Outline Groups naming insurance policies – Energetic Listing FAQ


What choices does Microsoft 365 supply for outlining Groups naming insurance policies? If Groups is to be launched within the firm, a governance
idea should be created beforehand. This idea clarifies, for instance, how teams and groups are created, which safety guidelines apply, whether or not visitor entry is permitted, how naming is regulated, and way more. In one of the best case, it also needs to be doable to make sure that all the foundations of the governance idea may be utilized technically.

On this article I wish to have a look at the choices for implementing the naming coverage. After looking the Microsoft documentation, one can find an outline of the Microsoft 365 group naming coverage and how you can implement this coverage by way of Azure Energetic Listing. Since every Microsoft Groups crew is mapped to its personal Microsoft 365 teams, this appeared like the suitable method.

So I logged on to my take a look at setting and tried the entire thing out.

Establishing the groups naming conventions

If we need to outline the groups naming coverage, we first go to the Azure AD Administration Portal. There we choose the “Teams” part beneath “All Providers” and go to the “Naming Coverage” merchandise within the menu beneath Settings.

Right here we are able to make two naming coverage settings:

  • Blocked phrases: These phrases should not seem in group names. This permits us to exclude phrases which are reserved for particular teams, e.g. CEO or Administration. These phrases are uploaded by way of a CSV file.
  • Naming coverage for teams: Prefix and suffix of the group title may be outlined right here. A prefix or suffix can encompass a number of components.
    Fastened strings or values from person attributes of the person who creates the crew are doable. The group title may be as much as 53 characters lengthy, together with the prefix and suffix.
    When specifying the person attributes, the Azure AD attributes “Division”, “Firm”, “StateOrProvince”, “CountryOrRegion” and “Title” are presently supported. All unsupported attributes are handled as a hard and fast string, i.e. they’re transferred one-to-one to the group title.

For my take a look at, I’ll use solely the naming insurance policies for now. Since I need to outline guidelines for crew naming right here, I would like my group title to start out with the prefix “TEAM”. To know to which division a crew belongs, the division title also needs to be included within the group title. For this goal I get the worth of the “Division-Attribute” of the person within the prefix. To make it simpler to learn, the parts are separated with hyphen, in order that I nonetheless outlined a hard and fast string for “-” on the finish of the prefix.

The groups naming insurance policies ought to have this format: TEAM-[Department]- [Group Name].

These are the corresponding settings within the administration portal:

Group Naming policy - Microsoft Teams

Check: Create groups with title coverage

Now I open the Groups net consumer with my take a look at person Alex and create a brand new crew.

I select the “Handle a challenge” template.


There are already just a few settings, reminiscent of 4 channels and 4 apps.


For my take a look at, I would like it to be public for as soon as, because it’s a compartmentalized take a look at setting. That is simpler for my exams.

Then we’d like an acceptable title. The announcement of my remaining crew title already seems good.

LightSpeed

The crew has been created, we’re… performed!
However…wait a minute! One thing has gone flawed.

Team's name

The appliance of the title rule didn’t work as anticipated. The prefix seems twice and a significant “undefined” was appended to the top of the title.

Microsoft 365 Group

The related Microsoft 365 group seems simply as flawed.

Create groups by customers Evaluation: Groups double-barrelled designation insurance policies

So why isn’t it working? Did I make an enter error through the creation?
So I create a crew once more with the “Handle a challenge” template as a public crew. The identical conduct. Likewise as a non-public crew.
Then I create a crew with out a template, with the default setting “From the start”.
And… it really works!

The corresponding Microsoft 365 group seems right too.

So it’s as much as the template!
The preliminary examination of the template settings has not yielded any extra detailed findings. Additional investigation is important. Nonetheless, that is to be the content material of a future article.


Abstract

We discovered how naming insurance policies may be outlined in Azure AD and the way they work when creating groups.
This technique is an effective method however not relevant in observe.

  • Just one rule may be outlined. Even when the rule may be constructed dynamically, that is too little to have the ability to map totally different crew classes, for instance.
  • The rule acts globally on all Microsoft 365 teams and derived assets. A granular and managed method is completely
    vital in sensible use.
  • There seems to be a bug in the usage of groups templates. Which means naming conventions can not presently be used when utilizing Groups templates. my-IAM TeamSpace is the secure different for utilizing templates together with naming conventions.

 

FirstAttribute AG

 
Extra query about Azure AD and Microsoft Groups? Help wanted?

Contact us
  

 

Article created: 15.02.2021

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments