Closed GruberMarkus closed 1 year ago
Let's walk through the authentication stack. If you try the following command (replace the variables by your values):
Connect-IPPSsession -AppId $appId -CertificateThumbprint $thumbprint -Organization $tenantId
Get-AutoSensitivityLabelPolicy
Are you getting the same error? If so, then that is either a permission or a licensing issue.
The test commands always worked, Get-AutoSensitivityLabelPolicy only failed in M365DSC.
Upgrading to the newest version solved the issue immediately, although I do not see why.
You can close this issue.
Thanks for your support!
Thanks for the feedback!
Hi Guys Thanks for you guys great work on this. I am getting the same error and not sure that it is resolved. I have run this as Global Administrator (including explicit Compliance Administrator role).
I have followed @NikCharlebois suggestion of;
_Let's walk through the authentication stack. If you try the following command (replace the variables by your values):
Connect-IPPSsession -AppId $appId -CertificateThumbprint $thumbprint -Organization $tenantId Get-AutoSensitivityLabelPolicy Are you getting the same error? If so, then that is either a permission or a licensing issue._
....and can confirm I cannot see it. I work for an organisation that has A5 licencing.
I can confirm that I have access to this data through the Purview portal itself. What other permission is\can be required?
Many thanks
What m365dsc version are you using and could run Update-M365DSCDependencies and Uninstall-M365DSCOutdatedDependencies to confirm your machine’s setup?
Hi @andikrueger - that was quick thank you.
M365DSC version is 1.23.621.1 ExchangeOnlineManagement version is 3.2.0
I updated this morning :)
Are there any other versions of EXOManagementShell on your system?
Hi Andi
No. The exchange module is also installed under the AllUsers scope - C:\Program Files\WindowsPowerShell\Modules.
@andikrueger & @NikCharlebois, can you confirm that the license (A5) and Global Administrator (including explicit Compliance Administrator role) permission should be sufficient get access to these to resources?
Thanks again for your time :)
From: Andi Krüger @.> Sent: Friday, 23 June 2023 3:27 PM To: microsoft/Microsoft365DSC @.> Cc: Northism @.>; Comment @.> Subject: Re: [microsoft/Microsoft365DSC] SCAutoSensitivityLabelPolicy, SCAutoSensitivityLabelRule: Cmdlets Set-AutoSensitivityLabelRule and Get-AutoSensitivityLabelPolicy not found (Issue #3313)
Are there any other versions of EXOManagementShell on your system?
— Reply to this email directly, view it on GitHubhttps://github.com/microsoft/Microsoft365DSC/issues/3313#issuecomment-1603851597, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACG75ZCURAJXEE4VYELUEB3XMVAO7ANCNFSM6AAAAAAYDN55XQ. You are receiving this because you commented.Message ID: @.***>
FYI
I have opened up a ticket with MS and will provide feedback here once I have a resolution.
@Northism Did you have a chance to review this section of our documentation: https://microsoft365dsc.com/user-guide/get-started/authentication-and-permissions/#security-and-compliance-center-permissions @NikCharlebois added this section a few days ago.
@andikrueger - I hadn't seen it. Thanks for the update.
I have had feedback from MS. The issue I have is a licensing issue. My version of A5 license doesn't have the auto-labelling available in my Non-Prod tenant.
Thanks you for your support.
Details of the scenario you tried and the problem that is occurring
SCAutoSensitivityLabelPolicy andSCAutoSensitivityLabelRule can not be exported because PowerShell Cmdlets can not be found. All other security and compliance ressources work fine.
Verbose logs showing the problem
Suggested solution to the issue
No suggestion.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
OsName : Microsoft Windows 10 Enterprise OsOperatingSystemSKU : EnterpriseEdition OsArchitecture : 64-Bit WindowsVersion : 2009 WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406 OsLanguage : de-DE OsMuiLanguages : {de-DE}
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.510.1