BUG?: [SPOSharingSettings] Settings appear to apply, except for RequireAcceptingAccountMatchInvitedAccount = $True about microsoft365dsc HOT 7 OPEN

I'm also having the same issue but it's definitely a backend problem and not specific to M365DSC since my integration tests were working before in changing this specific property to true and now it doesn't.

from microsoft365dsc.

@ykuijs Hi, are you aware of this issue? The cmdlet was working before and now it doesn't so it's a backend problem which seems to be affecting other people.

A simple way to replicate this is to first make sure that the property is set to $false and then do the below, no error messages are shown even with Verbose and Debug enabled.

Set-PnPTenant -RequireAcceptingAccountMatchInvitedAccount $true
(Get-PnPTenant).RequireAcceptingAccountMatchInvitedAccount # this always returns $false

from microsoft365dsc.

UPDATE: We modified more settings to this resource , which seem to apply as expected - EXCEPT for RequireAcceptingAccountMatchInvitedAccount. It remains "off"/$false, regardless of what we do.

Here is the resource config
BccExternalSharingInvitations = $False;
Credential = $***;
DefaultLinkPermission = "View";
DefaultSharingLinkType = "AnonymousAccess";
EnableGuestSignInAcceleration = $False;
Ensure = "Present";
ExternalUserExpirationRequired = $True;
ExternalUserExpireInDays = 30;
FileAnonymousLinkType = "Edit";
FolderAnonymousLinkType = "Edit";
IsSingleInstance = "Yes";
MySiteSharingCapability = "Disabled";
NotifyOwnersWhenItemsReshared = $True;
PreventExternalUsersFromResharing = $True;
ProvisionSharedWithEveryoneFolder = $False;
#this is the only value that does not deploy:
RequireAcceptingAccountMatchInvitedAccount = $True;
SharingCapability = "ExternalUserAndGuestSharing";
SharingDomainRestrictionMode = "None";
ShowAllUsersClaim = $False;
ShowEveryoneClaim = $False;
ShowEveryoneExceptExternalUsersClaim = $True;
ShowPeoplePickerSuggestionsForGuestUsers = $True;

from microsoft365dsc.

I'm seeing the same (unwanted) behaviour.

from microsoft365dsc.

I'm also having the same issue but it's definitely a backend problem and not specific to M365DSC since my integration tests were working before in changing this specific property to true and now it doesn't.

Sounds plausible, as other values in this resource deploy as expected.

@NikCharlebois any chance to get this fed back to whatever team at MSFT owns this setting?

from microsoft365dsc.

If the behavior also occurs when running Set-PnPTenant directly, it has something to do with PnP PowerShell. Could you please create an issue in the PnP PowerShell repo: https://github.com/pnp/powershell/issues

At the same time, I will check with a contact in that team

from microsoft365dsc.

@ykuijs The thing is that this was working just a couple weeks before and nothing changed relative to the PnP module, we don't have updates to it in ages so it's clearly a backend issue, are they able to help with that?

from microsoft365dsc.