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

Excel Report generated from M365DSC has different values than the exported Tenant Configuration #2503

Closed
atdheekurteshi opened this issue Nov 8, 2022 · 4 comments · Fixed by #2531 or #2546
Labels
Bug Something isn't working Teams

Comments

@atdheekurteshi
Copy link

atdheekurteshi commented Nov 8, 2022

Details of the scenario you tried and the problem that is occurring

SCRetentionCompliancePolicy -Name 'Microsoft Teams Chat Standard Retention Policy' - TeamsChatLocation has a NULL value after the Excel report its generated through powershell but on the Tenant the value its equel to TeamsChatLocation = All and it is right configured.

Please have a look down below.

New-M365DSCReportFromConfiguration -Type Excel -ConfigurationPath x -OutputPath x
SCRetentionCompliancePolicy | Name | Microsoft Teams Chat Standard   Retention Policy
-- | -- | --
SCRetentionCompliancePolicy | Comment | Standard Aufbewahrungsrichtlinie für Microsoft Teams Chat   Protokolle
SCRetentionCompliancePolicy | Enabled | FALSCH
SCRetentionCompliancePolicy | Ensure | Present
SCRetentionCompliancePolicy | ResourceID | 7a8623fc-326b-4b9e-b327-490e23ad68b5
SCRetentionCompliancePolicy | RestrictiveRetention | FALSCH
SCRetentionCompliancePolicy | TeamsChannelLocation | $Null
SCRetentionCompliancePolicy | TeamsChannelLocationException | $Null
SCRetentionCompliancePolicy | TeamsChatLocation | $Null
SCRetentionCompliancePolicy | TeamsChatLocationException | $Null
# For additional information on how to use Microsoft365DSC, please visit https://aka.ms/M365DSC
param (
   [parameter()]
   [System.Management.Automation.PSCredential]
   $Credential
)

Configuration M365TenantConfig
{
   param (
       [parameter()]
       [System.Management.Automation.PSCredential]
       $Credential
   )

   if ($null -eq $Credential)
   {
       <# Credentials #>
       $Credscredential = Get-Credential -Message "Credentials"

   }
   else
   {
       $CredsCredential = $Credential
   }

   $OrganizationName = $CredsCredential.UserName.Split('@')[1]

   Import-DscResource -ModuleName 'Microsoft365DSC' -ModuleVersion '1.22.1102.1'

   Node localhost
   {
      
       
       SCRetentionCompliancePolicy 7a8623fc-326b-4b9e-b327-490e23ad68b5
       {
           Comment                       = "Standard Aufbewahrungsrichtlinie für Microsoft Teams Chat Protokolle";
           Credential                    = $Credscredential;
           Enabled                       = $False;
           Ensure                        = "Present";
           Name                          = "Microsoft Teams Chat Standard Retention Policy";
           RestrictiveRetention          = $False;
           TeamsChannelLocation          = @();
           TeamsChannelLocationException = @();
           TeamsChatLocation             = @(All);
           TeamsChatLocationException    = @();
       }
   }
}

M365TenantConfig -ConfigurationData .\ConfigurationData.psd1 -Credential $Credential

#### The operating system the target node is running
<!--
    Please provide as much as possible about the target node, for example
    edition, version, build and language.
    On OS with WMF 5.1 the following command can help get this information.

OsName               : Microsoft Windows 10 Pro
OsOperatingSystemSKU : 48
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage           : en-US
OsMuiLanguages       : {en-US, de-DE}

-->

#### Version of the DSC module that was used ('dev' if using current dev branch)
1.22.1102.1
@andikrueger
Copy link
Collaborator

Please provide more information on this issue.

@atdheekurteshi
Copy link
Author

@andikrueger Information where provided.

@andikrueger
Copy link
Collaborator

Could you try to place All in Quotes?

@malauter
Copy link
Member

malauter commented Nov 8, 2022

This is maybe related to #2472 and #2471. Seems that 'All' is stored as empty value for TeamsChatLocation, but could not find any clear documentation on it. If I try to configure this manually with PowerShell, the property also stays empty if I set it to All.

@andikrueger andikrueger added Bug Something isn't working Teams and removed Pending Information Core Engine labels Nov 8, 2022
NikCharlebois added a commit to NikCharlebois/Microsoft365DSC that referenced this issue Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Teams
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants