Forum Discussion
Enoll
Jul 20, 2021Copper Contributor
Set-SPOSite Conditional Access Error (AuthContextStrength)
Hello,
We have set AllowLimitedAccess for quite some time to our sites with the same command:
Set-SPOSite -Identity IdentityHere -ConditionalAccess AllowLimitedAccess
Until today, when it suddenly threw an error : Set-SPOSite : Field or property "AuthContextStrength" does not exist.
Tried on couple of other test tenants but still the same issue. The problem is also not for a specific site but for all sites.
Any suggestions would be much appreciated
- Looks like you can pass a Site object to Set-SPOTenant like this
get-sposite https://domain.tld/site/ | set-spotenant -ConditionalAccessPolicy AllowLimitedAccess
Tested it and successfully changed the ConditionalAccessPolicy for that site. (Not the Tenant) - sushilmaurya71305Copper ContributorSet-SPOSite : Field or property "AuthContextStrength" does not exist.
At line:1 char:1
"SAME ERROR"... - Osh_A415Copper ContributorSet-SPOSite : Field or property "AuthContextStrength" does not exist.
At line:1 char:1
"SAME ERROR"...- Bruno Aleixo
Microsoft
Osh_A415 we are currently investigating this behavior
- dcoberBrass ContributorAny updates on this? I haven't seen any updates to the SharePoint Online PowerShell module, only the PnP module.
- nygarm1Copper Contributor
Same here:
Get-PnPTenantSite : The property or field 'AuthContextStrength' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly
requested. - EnollCopper ContributorSame here, everything used to work up until Monday, Tuesday suddenly it stopped.
- Mike OliveiraCopper Contributor
I am getting the same error on my tenant for PnP.PowerShell (Powershell Core)
Get-PnPTenantSite
Seems like something broke on the Microsoft side
- IMCopper ContributorOkay, MS changed the something.
In PnP.PowerShell it was fixed:
https://github.com/pnp/powershell/commit/22985f6f3d15c0d23919a24288d7f92a175c2ab9