Skip to content
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

PPTenantIsolationSettings Rules causing issues with New-M365DSCDeltaReport #5110

Open
adambrubaker opened this issue Sep 27, 2024 · 3 comments

Comments

@adambrubaker
Copy link

Description of the issue

Hello

We made a change to out Power Platform Tenant Isolation settings that is causing the New-M365DSCDeltaReport command to fail. It looks like our new Rules are causing the issue. I have tested this out by manually removing the new Rules section of the config and the command completes fine.

Previous configuration

        PPTenantIsolationSettings "PPTenantIsolationSettings"
        {
            ApplicationId         = $ConfigurationData.NonNodeData.ApplicationId;
            CertificateThumbprint = $ConfigurationData.NonNodeData.CertificateThumbprint;
            Enabled               = $False;
            IsSingleInstance      = "Yes";
            TenantId              = $OrganizationName;
        }

New configuration

        PPTenantIsolationSettings "PPTenantIsolationSettings"
        {
            ApplicationId         = $ConfigurationData.NonNodeData.ApplicationId;
            CertificateThumbprint = $ConfigurationData.NonNodeData.CertificateThumbprint;
            Enabled               = $False;
            IsSingleInstance      = "Yes";
            Rules                 = @(MSFT_PPTenantRule {
                TenantName          = 'f01e930a-b52e-42b1-b70f-a8882b5d043b'
                Direction           = 'Inbound'
            }
MSFT_PPTenantRule {
                TenantName          = '5c3b7814-ca65-43ac-a02e-9b3c9f32c001'
                Direction           = 'Outbound'
            }
MSFT_PPTenantRule {
                TenantName          = 'b4c9f32e-da17-4ded-9c95-ce9da38f25d9'
                Direction           = 'Inbound'
            }
MSFT_PPTenantRule {
                TenantName          = 'f8cdef31-a31e-4b4a-93e4-5f571e91255a'
                Direction           = 'Outbound'
            }
MSFT_PPTenantRule {
                TenantName          = '7e4d5797-1b9b-4d27-b157-725044628ce2'
                Direction           = 'Outbound'
            }
MSFT_PPTenantRule {
                TenantName          = 'f65f8155-9694-4d3b-8a9e-000ffd3d7a6f'
                Direction           = 'Inbound'
            }
            );
            TenantId              = $OrganizationName;
        }

Here is the error that I am seeing
image

Microsoft 365 DSC Version

1.24.904.1

Which workloads are affected

Power Platform

The DSC configuration

New-M365DSCDeltaReport -Source 'C:\temp\dsc\DSC_PowerPlatform_09252024.ps1' -Destination 'C:\temp\dsc\DSC_PowerPlatform_09262024.ps1' -OutputPath 'C:\temp\dsc\deltareport.html'

Verbose logs showing the problem

No response

Environment Information + PowerShell Version

OsName               : Microsoft Windows 11 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 22621.1.amd64fre.ni_release.220506-1250
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

Name                           Value
----                           -----
PSVersion                      5.1.22621.4111
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.4111
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
@ricmestre
Copy link
Contributor

winrm quickconfig -force

@DennisLangenberg
Copy link

Was this resolved ? having similar error in assertblueprint but seems to be due to version of DSC in combination with specific blueprint files works with old version 1.24.110.1 not with newer

@adambrubaker
Copy link
Author

No not resolved. To be fair I haven't made any changes. Still waiting on a direction of what to try. Do you think rolling back to 1.24.110.1 will work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants