SPOTenantSettings - OneDriveSharingCapability throws error in Set-TargetResource

[salbeck-sit]

Description of the issue

When applying SPOTenantSettings I received the following error-message which I haven't seen before.

PowerShell DSC resource MSFT_SPOTenantSettings failed to execute Set-TargetResource functionality with error message: {
"odata.error":{"code":"-1, Microsoft.SharePoint.Client.InvalidClientQueryException","message":{"lang":"en-US","value":"T
he property 'OneDriveSharingCapability' does not exist on type 'Microsoft.Online.SharePoint.TenantAdministration.Tenant'
. Make sure to only use property names that are defined by the type."}}}

It's been a while and this may be the first time I've used the resource since it was changed to use Invoke-PnPSPRestMethod. Maybe this property should be removed from the resource in the next 'breaking release'.
It already exists in SPOSharingSettings where it is called MySiteSharingCapability.
FWIW, the property is not defined in the configuration being applied.

Microsoft 365 DSC Version

DEV

Which workloads are affected

SharePoint Online

The DSC configuration

SPOTenantSettings "SPOTenantSettings"
        {
            ApplicationId                                          = $ConfigurationData.NonNodeData.ApplicationId;
            ApplyAppEnforcedRestrictionsToAdHocRecipients          = $True;
            CertificateThumbprint                                  = $ConfigurationData.NonNodeData.CertificateThumbprint;
            CommentsOnSitePagesDisabled                            = $False;
            Ensure                                                 = "Present";
            ExemptNativeUsersFromTenantLevelRestricedAccessControl = $False;
            FilePickerExternalImageSearchEnabled                   = $True;
            HideDefaultThemes                                      = $False;
            IsSingleInstance                                       = "Yes";
            LegacyAuthProtocolsEnabled                             = $False;
            MarkNewFilesSensitiveByDefault                         = "AllowExternalSharing";
            MaxCompatibilityLevel                                  = "15";
            MinCompatibilityLevel                                  = "15";
            NotificationsInSharePointEnabled                       = $True;
            OfficeClientADALDisabled                               = $False;
            OwnerAnonymousNotification                             = $True;
            PublicCdnAllowedFileTypes                              = "CSS,EOT,GIF,ICO,JPEG,JPG,JS,MAP,PNG,SVG,TTF,WOFF";
            PublicCdnEnabled                                       = $False;
            SearchResolveExactEmailOrUPN                           = $False;
            SignInAccelerationDomain                               = "";
            SocialBarOnSitePagesDisabled                           = $False;
            TenantDefaultTimezone                                  = "(UTC+01:00) Brussels, Copenhagen, Madrid, Paris";
            TenantId                                               = $OrganizationName;
            UseFindPeopleInPeoplePicker                            = $False;
            UsePersistentCookiesForExplorerView                    = $False;
        }

Verbose logs showing the problem

Environment Information + PowerShell Version

[bartvermeersch]

OneDriveSharingCapability was added in #5749

But it doesn't seem to exist on that endpoint as a property (https://xxxx-admin.sharepoint.com/_api/SPO.Tenant?$select=OneDriveSharingCapability) and is already available through another resource SPOSharingSettings (MySiteSharingCapability) as pointed out by @salbeck-sit

[FabienTschanz]

Are you okay with removing the property since it's obviously not supported?

[salbeck-sit]

by all means - even if it's a breaking change

[salbeck-sit]

@FabienTschanz Not sure how far out the next breaking release is but since the PR hasn't yet been merged the error perists.
A stop-gap measure is a non-breaking PR where the property isn't removed but marked as deprecated and ignored by code. Any chance of doing that soon?

[FabienTschanz]

@salbeck-sit The next breaking change release will be in October. In two or three weeks, the PRs will be merged and prepared for release.

[salbeck-sit]

I'll have to live with that. In the meantime I'm using a local version of the resource.