Jul 20 2021 12:24 AM - edited Jul 20 2021 12:45 AM
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
Jul 20 2021 07:26 AM
@Enoll
Hi,
I have the same problems with PnP.PowerShell (Powershell Core) since today (yesterday everything worked).
PS: The old (deprecated) SharePointPnPPowerShellOnline module works.
Jul 20 2021 08:11 AM
I am getting the same error on my tenant for PnP.PowerShell (Powershell Core)
Get-PnPTenantSite
Seems like something broke on the Microsoft side
Jul 20 2021 08:15 AM
Jul 20 2021 09:05 AM
no it has not been fixed yet.
Jul 20 2021 09:27 AM
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.
Jul 20 2021 11:49 AM
Jul 20 2021 02:29 PM
Jul 20 2021 11:58 PM
Jul 21 2021 12:18 AM
So, the new nightly 1.6.44 is out and it works again.
https://www.powershellgallery.com/packages/PnP.PowerShell/1.6.44-nightly
Jul 21 2021 06:56 AM
@IM That only fixes it for people who are using PnP.PowerShell. Does anyone know what we can do about the standard SharePoint Management PowerShell?
Jul 21 2021 10:12 AM
Jul 23 2021 02:00 AM
@Osh_A415 we are currently investigating this behavior
Jul 26 2021 04:22 AM
Jul 26 2021 05:28 AM
Thank you, Do you have any updates on this issues ? I had run share point power shell this morning ang getting same error ? @Bruno Aleixo
Jul 26 2021 11:13 AM
Jul 26 2021 06:48 PM
I resolved by updating the Powershell ISE to use a new version of Powershell as well as updating the
Aug 03 2021 06:16 AM
Aug 03 2021 06:27 AM
Nevermind, I see the update in the message center now :)
Current status: Following our internal testing and validation, we've deployed our code fix to the affected environments. We're monitoring the fix deployment as it is safely implemented through our change management process, and are expecting for it to have remediated impact by Monday, August 23, 2021.