You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Sharepoint admin setting for policy 1.4 "Guests must sign in using the same account to which sharing invitations are sent", backend field RequireAcceptingAccountMatchInvitedAccount looks like it is being deprecated or simply ignored. We can no longer locate this setting in any of the test tenant Sharepoint admin centers and when we execute the code below, it does nothing and the value of the variable always comes back false. We are not the only ones experiencing this problem.
It is not clear yet but we might need to turn off or remove this from Scuba, because it doesn't make sense to have a policy that A) doesn't exist in the admin center and B) the user cannot configure via Powershell either.
Set-PnPTenant -RequireAcceptingAccountMatchInvitedAccount $true
(Get-PnPTenant).RequireAcceptingAccountMatchInvitedAccount # this always returns $false
This is the respective setting described in the baseline.
The text was updated successfully, but these errors were encountered:
tkol2022
added
the
bug
This issue or pull request addresses broken functionality
label
Aug 7, 2024
🐛 Summary
The Sharepoint admin setting for policy 1.4 "Guests must sign in using the same account to which sharing invitations are sent", backend field RequireAcceptingAccountMatchInvitedAccount looks like it is being deprecated or simply ignored. We can no longer locate this setting in any of the test tenant Sharepoint admin centers and when we execute the code below, it does nothing and the value of the variable always comes back false. We are not the only ones experiencing this problem.
It is not clear yet but we might need to turn off or remove this from Scuba, because it doesn't make sense to have a policy that A) doesn't exist in the admin center and B) the user cannot configure via Powershell either.
This is the respective setting described in the baseline.
The text was updated successfully, but these errors were encountered: