BUG?: [SPOSharingSettings] Settings appear to apply, except for RequireAcceptingAccountMatchInvitedAccount = $True #4771
Comments
GeldHades27355
changed the title
GeldHades27355
changed the title
|
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 |
|
I'm seeing the same (unwanted) behaviour. |
|
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? |
|
@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 |
|
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 |
|
@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? |
Description of the issue
Apologies if this is a noob question, but we're only starting out so I might not be asking the right questions in the right places.
We think we finally have a devops CI/CD pipeline running and it seems to execute without errors. I seems to connect to the right target tenant and subscription AND it correctly identifies a different configuration:
Target = [RequireAcceptingAccountMatchInvitedAccount, False]
Desired config = [RequireAcceptingAccountMatchInvitedAccount, True]
(we're only testing with ONE resource for now)
The log suggests that the LCM executes and applies the change (does it tho?), but even an hour later, the target tenant still hasn't implemented [RequireAcceptingAccountMatchInvitedAccount, True]. We verified this through the GUI and with an M365DSC export of that resource, which are both consistent.
What would cause the setting to not apply? Where should we start looking?
Microsoft 365 DSC Version
1.24.605.1
Which workloads are affected
SharePoint Online
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: