-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG? [SPOSharingSettings] throws error: "the member BccExternalSharingInvitations is not valid" #4786
Comments
You have some problem in your blueprint, according to the screenshot you are using that property |
hmmm... it seems to be in the documenation tho: https://microsoft365dsc.com/resources/sharepoint/SPOSharingSettings/ Also, this isn't a blueprint - we're just re-importing an export raw to another tenant. The output from this: Export-M365DSCConfiguration -Components @("AADSecurityDefaults", "EXOMailTips", "IntuneDeviceCompliancePolicyWindows10", "IntuneDeviceConfigurationEmailProfilePolicyWindows10", "O365OrgSettings", "ODSettings", "SCSensitivityLabel", "SPOSharingSettings", "TeamsUpgradePolicy") -Credential $Credential is, verbatim, the DSC code I posted above. BccExternalSharingInvitations is ONLY contained in SPOSharingSettings, nowhere else. |
The result of the export is called a blueprint, the file M365TenantConfig.ps1 is your blueprint. The errors shown in your screenshot show that the property appears in several lines, you need to investigate why they ended up there. |
It runs three times due to a bug in our DevOps Agent config. But that shouldn't cause the parameter to fail, since it seems to be exactly where it should be. It should succeed three times, if anything, shouldn't it? Here is the entire code: param ( Configuration M365TenantConfig
} M365TenantConfig -ConfigurationData .\ConfigurationData.psd1 -Credential $Credential |
I'm able to compile the blueprint to MOF just fine so try to uninstall M365DSC module, update to latest version, make a new export and try again. |
Yes, the mof always compiles fine - locally. However, we do that with Azure DevOps agents on a remote server, which is where the error occurs. I added info on the remote host to the initial post. Maybe it'll give some insight as to why that parameter fails. (others work fine, btw, also other resources). This looks way too specific IMHO to be a an external problem. |
Latest version is 1.24.619.1, M365DSC has weekly releases. I also use DevOps and have an whole lot of pipelines working, one of them also does exports automatically and I don't have this problem so this is something specific to your environment. Connect to the host where the agent is installed, upgrade M365DSC and try again as I said, if you still have the same problem you need to checkout that file on the host because it's clearly telling you that the property is showing up in several lines. |
OK - will do. Thanks! While we're on it: surely, we're not expected to update weekly? 😉 That'll be VERY hard/risky to do once we reach a few hundred tenants IMHO. |
Never mind - we can't repro this anymore. Closing this for now. |
Description of the issue
We pulled an export of our master tenant, and [SPOSharingSettings] seems to be problematic (also see #4771).
We're getting "
the member BccExternalSharingInvitations is not valid
", when trying to apply this resource.According to the documentation, this should be a valid parameter, AND the export contains it as well.
Is this a bug? Or is there a special trick to make this parameter work?
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
OsName : Microsoft Windows Server 2022 Standard Evaluation
OsOperatingSystemSKU : 79
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 20348.1.amd64fre.fe_release.210507-1500
OsLanguage : en-US
OsMuiLanguages : {en-US, de-DE}
Name Value
PSVersion 5.1.20348.2400
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.20348.2400
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
The text was updated successfully, but these errors were encountered: