Get-MSOLUser has a standard limitation of 500 so the all flag allows us to bring all profile

Great so now I have title with the sku I need to used to find my personal student consumer base since all my personal students must certanly be licensed with that sku. To be certain I’m able to run a simple PowerShell demand to create a list of the users which have that license. I’m going to do so and also they display straight inside the PowerShell window since I only have 18 users nevertheless may want to dispose of it to a CSV inside production conditions.

  1. In this exact same PowerShell windows run: get-msoluser -all | where-object
  2. As soon as that operates you will want to discover a list such as this:

Realize that I have a€?-all’ placed in the command after a€?get-msoluser’ though avoid the use of they in my own screen photos; simply because my scholar count are 18 however your’s could be more. Everything in my student licenses export looks good therefore I now understand I am able to pick on merely my students by her license and make use of that to assign our very own newly produced texting coverage!

Assigning the messaging plan to simply college students considering her permit

We intend to merge the PowerShell demand from above that individuals accustomed read all people because of the licenses of M65EDU_A5_STUDENT using the Cs-TeamsMessagingPolicy command to next put it on to the people consumers.

To achieve this we will need an adjustable to accommodate the customers we pull in and then pipe those people in to the Cs-Teams demand. Lower is what the general command looks like: $members=get-msoluser -all | where-object

Let us break up that demand actual quick:a€“ $members will be the changeable that can house the customers we are pulling ina€“ Get-MSOLUser is actually a general command when working with users in Azure post / company 365a€“ we have been next selecting individual items that have an AccountSkuID complement of a€?M365EDU_A5_STUDENTa€?

Once they works we could next merely type $customers and click submit to see the entire list (once again you really need to pipe your own to a CSV for evaluation in manufacturing). Below you will see both the preliminary command operate in conjunction with me personally reviewing the members inside the varying:

Our company is today prepared to move forward along with his, and all sorts of various other children, to your new no speak coverage

Before we change the texting rules let’s see what students is now designated so that as soon as we continue with this modification we now have something to compare. Inside groups Admin Center choose Users for the left hand navigation pane.

We can note that Al has actually 9 worldwide guidelines assigned and 0 per-user strategies designated. This implies he or she is just allotted to worldwide default plans which we are able to confirm by hanging throughout the policies designated book.

We can furthermore validate exactly what messaging rules was used on students by run the annotated following: Get-CsOnlineUser -Identity userUPN | ft DisplayName, TeamsMessagingPolicy

We could read my sample beginner Al has nothing noted for Messaging coverage because they are designated the Global standard:

Quick suggestion: when making large-scale variations via PowerShell it might be smart to break this up into batches. Do not protect how exactly to do this in this post but definitely one thing to start thinking about.

If you find yourself prepared replace the messaging rules assignment to all your youngsters make use of the same PowerShell admin windows from earlier operated this order: foreach($affiliate in $members)

Let’s break up that command genuine quick:a€“ we’re running a foreach and producing a short-term adjustable of $representative which will be always run user by user from your a number of $membersa€“ we are subsequently incorporating the insurance policy (giving) of a€?EDU No Private Chata€? that we created earlier to each and every member utilizing their UserPrincipalName from your $customers list