Home

Teams Meeting Policies

%3CLINGO-SUB%20id%3D%22lingo-sub-216450%22%20slang%3D%22en-US%22%3ETeams%20Meeting%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216450%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20our%20Teams%20Meeting%20policy%2C%20we%20want%20our%20AutoAdmittedUsers%20parameter%20set%20to%20%22Everyone%22%20rather%20than%20the%20default%20%22EveryoneInCompany%22.%20I%20was%20able%20to%20change%20this%20in%20the%20Global%20policy%20with%20%3CSPAN%3ESet-CsTeamsMeetingPolicy%3C%2FSPAN%3E%2C%20but%20it%20does%20not%20seem%20to%20be%20applying.%20I%20tried%20to%20use%20Grant-CsTeemsMeeting%20policy%2C%20but%20it%20treats%20global%20as%20null%20(I%20assume%20because%20it's%20the%20org-wide%20default).%20Some%20of%20our%20users%20also%20have%20%22RestrictedAnonymousAccess%22%20Meeting%20policy%20applied%2C%20and%20I'm%20not%20sure%20how%20or%20why%20this%20was%20applied.%20(Also%20unable%20to%20change%20user%20level%20policies%20at%20the%20moment%2C%20I%20assume%20functionality%20is%20not%20rolled%20out%20for%20it%20yet).%20Does%20anyone%20know%20if%20people%20with%20%22none%22%20for%20Policies%20assigned%20should%20be%20getting%20the%20Global%20default%3F%20Or%20are%20Meeting%20Policies%20just%20not%20enabled%20at%20all%20yet%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-216450%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301418%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301418%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20adjusted%20mine%20as%20well.%26nbsp%3B%20I%20was%20surprised%20at%20how%20many%20users%20had%20legacy%20policy%20settings.%26nbsp%3B%20My%20guess%20is%20it%20is%20because%20we%20started%20SFB%20to%20Teams%20very%20early%20on.%26nbsp%3B%20Here%20is%20what%20I%20ran%20to%20baseline%20everyone%20(I%20have%20no%20custom%20policies%20yet)....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%24Users%20%3D%20get-csonlineuser%20%7C%20where%20%7B%24_.teamsmeetingpolicy%20-ne%20%24null%7D%3CBR%20%2F%3Eforeach%20(%24user%20in%20%24users)%20%7BGrant-csteamsmeetingpolicy%20%24user.userprincipalname%20-PolicyName%20%24null%7D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20ran%26nbsp%3BSet-CsTeamsMeetingPolicy%20-Identity%20Global%20-AutoAdmittedUsers%20Everyone%20because%20the%20lobby%20is%20big%20hangup%20for%20a%20lot%20of%20people.%26nbsp%3B%20They%20just%20want%20it%20to%20work%20like%20Slack%20%2F%20Zoom%20%2F%20Webex%20etc...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292845%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292845%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20adjusted%20my%20Global%20policy%20to%20%22allow%20anonymous%20users%20to%20start%20meetings%22%20and%20%22automatically%20admit%20Everyone%22%2C%20so%20no%20more%20Lobby.%26nbsp%3B%20I%20then%20did%20Grant-csteamsmeetingpolicy%20to%20get%20rid%20of%20restrictedanonymousaccess%20for%20anyone%20that%20had%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20new%20meetings%20work%20properly%20now%20-%20no%20one%20has%20to%20wait%20in%20the%20lobby%20including%20those%20who%20only%20use%20telephone%20to%20join%2C%20but%20meetings%20that%20were%20scheduled%20previously%20adhere%20to%20the%20policy%20that%20was%20in%20place%20when%20the%20meeting%20was%20created%2C%20i.e.%20they%20still%20have%20participants%20waiting%20in%20the%20lobby.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%2C%20is%20there%20any%20way%20to%20identify%20meetings%20created%20before%20a%20certain%20date%20(the%20date%20when%20I%20made%20the%20policy%20changes)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20all%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283750%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283750%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20you%20had%20to%20run%20that%20command%20for%20all%20users%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20users%20who%20have%20the%20AllOn..%20I%20have%20users%20who%20have%20the%20RestrictedAnonAccess..%20I%20don't%20know%20if%20I%20even%20have%20any%20users%20who%20are%20on%20global.%20Very%20weird.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-216513%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216513%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20anyone%20else%20is%20having%20this%20issue%2C%20it%20was%20Grant-CsTeamsMeetingPolicy%20-PolicyName%20%24null%20-Identity%20%22users%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-216494%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216494%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Steven%20-%20any%20idea%20why%20some%20of%20my%20users%20are%20being%20assigned%20the%20%22RestrictedAnonymousAccess%22%20Policy%20or%20how%20to%20unassign%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-216484%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Meeting%20Policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216484%22%20slang%3D%22en-US%22%3E%3CP%3ENone%20means%20global%2C%20if%20you%20look%20through%20the%20new%20admin%20center%20it%20shows%20it%20like%20this.%20You%20are%20right%20that%20user%20level%20policies%20aren't%20yet%20assignable%2C%20but%20will%20be%20very%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Doug Admin
New Contributor

Hi All,

 

For our Teams Meeting policy, we want our AutoAdmittedUsers parameter set to "Everyone" rather than the default "EveryoneInCompany". I was able to change this in the Global policy with Set-CsTeamsMeetingPolicy, but it does not seem to be applying. I tried to use Grant-CsTeemsMeeting policy, but it treats global as null (I assume because it's the org-wide default). Some of our users also have "RestrictedAnonymousAccess" Meeting policy applied, and I'm not sure how or why this was applied. (Also unable to change user level policies at the moment, I assume functionality is not rolled out for it yet). Does anyone know if people with "none" for Policies assigned should be getting the Global default? Or are Meeting Policies just not enabled at all yet?

 

 

6 Replies

None means global, if you look through the new admin center it shows it like this. You are right that user level policies aren't yet assignable, but will be very soon.

Thanks Steven - any idea why some of my users are being assigned the "RestrictedAnonymousAccess" Policy or how to unassign it?

 

If anyone else is having this issue, it was Grant-CsTeamsMeetingPolicy -PolicyName $null -Identity "users"

So you had to run that command for all users?

 

I have users who have the AllOn.. I have users who have the RestrictedAnonAccess.. I don't know if I even have any users who are on global. Very weird. 

I have adjusted my Global policy to "allow anonymous users to start meetings" and "automatically admit Everyone", so no more Lobby.  I then did Grant-csteamsmeetingpolicy to get rid of restrictedanonymousaccess for anyone that had it.

 

All new meetings work properly now - no one has to wait in the lobby including those who only use telephone to join, but meetings that were scheduled previously adhere to the policy that was in place when the meeting was created, i.e. they still have participants waiting in the lobby.

 

My question is, is there any way to identify meetings created before a certain date (the date when I made the policy changes)?

 

Thanks all

I just adjusted mine as well.  I was surprised at how many users had legacy policy settings.  My guess is it is because we started SFB to Teams very early on.  Here is what I ran to baseline everyone (I have no custom policies yet)....

 

$Users = get-csonlineuser | where {$_.teamsmeetingpolicy -ne $null}
foreach ($user in $users) {Grant-csteamsmeetingpolicy $user.userprincipalname -PolicyName $null}

 

I also ran Set-CsTeamsMeetingPolicy -Identity Global -AutoAdmittedUsers Everyone because the lobby is big hangup for a lot of people.  They just want it to work like Slack / Zoom / Webex etc...