Public/generated/Get-KritTcmTeamsClientConfiguration.ps1
|
<# ·· × × × ··· SirJ's Deaddrop ··· × × × ··· — If you found this, you were meant to — ---------------- A Seriously Kritical™ Production ---------------- [] → (¯`·.¸¸.·´¯) .·´ `·. [] → `·.______________.·´ | +------------------+ | | | Kritical™ | | | | [] [] | | | | | | | | [] [] [] | | | +------------------+ | (._.·´¯`·.¸_) Your last call. And your first move. ★ ☆ ★ +61 1300 274 655 sales at kritical dot net ----------------------------------------------------------------- .COPYRIGHT (c) 2026 Kritical Pty Ltd. All rights reserved. .AUTHOR Joshua Finley <joshua.finley@kritical.net> .COMPANY Kritical Pty Ltd | ABN 39 687 048 086 Level 4 / 60 Moorabool St Geelong VIC 3220 1300 274 655 | sales@kritical.net | https://kritical.net/ .NOTES HARD RULE 13 canonical Kritical branding — do not overlay other agent banners. Auto-generated by Generate-KritTcmFromM365DscSchema.ps1 (.1507o30+). Upstream reference: Microsoft365DSC by Microsoft (MIT). This shim provides literal search-replace equivalence — see Krit.TCM/generated/index.md. #> function Get-KritTcmTeamsClientConfiguration { <# .SYNOPSIS Krit.TCM shim for M365DSC resource TeamsClientConfiguration. .DESCRIPTION Auto-generated from M365DSC .schema.mof by scripts/m365-setup/Generate-KritTcmFromM365DscSchema.ps1 (.1507o30). Search-replace safe: callers that today invoke Get-M365DSCTeamsClientConfiguration -Credential $cred -TenantId $tid can rename to Get-KritTcmTeamsClientConfiguration -Credential $cred -TenantId $tid with ZERO other edits. Parameter shape matches the M365DSC .schema.mof exactly. Per operator direction, -PreferM365DscBehavior defaults to true. Actual Graph dispatch is delegated to Invoke-KritTcmM365DscSchemaBridge. Bridge maps resource → Graph endpoint per per-resource wave; where mapping is not yet shipped, bridge returns an object with Verdict='UNMAPPED'. .NOTES Workload: Teams Original mof: C:\Users\joshl\OneDrive - Kritical Pty Ltd\Github\KRTPax8ToShopifyConnector\.kritm365-mine\Microsoft365DSC\Modules\Microsoft365DSC\DSCResources\MSFT_TeamsClientConfiguration\MSFT_TeamsClientConfiguration.schema.mof Param count: 24 Generator wave: .1507o30 #> [CmdletBinding()] param( # Only valid value is 'Yes'. [Parameter(Mandatory)] [ValidateSet('Yes')] [string]$IsSingleInstance, # Designates whether users are able to leverage Box as a third party storage solution in Microsoft Teams. If $true, users will be able to add Box in the client and interact with the files stored there. [bool]$AllowBox, # Designates whether users are able to leverage DropBox as a third party storage solution in Microsoft Teams. If $true, users will be able to add DropBox in the client and interact with the files stored there. [bool]$AllowDropBox, # When set to $true, mail hooks are enabled, and users can post messages to a channel by sending an email to the email address of Teams channel. [bool]$AllowEmailIntoChannel, # Designates whether users are able to leverage GoogleDrive as a third party storage solution in Microsoft Teams. If $true, users will be able to add Google Drive in the client and interact with the files stored there. [bool]$AllowGoogleDrive, # Designates whether or not guest users in your organization will have access to the Teams client. If $true, guests in your tenant will be able to access the Teams client. Note that this setting has a core dependency on Guest Access being enabled in your Office 365 tenant. [bool]$AllowGuestUser, # When set to $true, users will be able to see the organizational chart icon other users' contact cards, and when clicked, this icon will display the detailed organizational chart. [bool]$AllowOrganizationTab, # Surface Hub uses a device account to provide email and collaboration services (IM, video, voice). This device account is used as the originating identity (the from party) when sending email, IM, and placing calls. As this account is not coming from an individual, identifiable user, it is deemed anonymous because it originated from the Surface Hub's device account. If set to $true, these device accounts will be able to send chat messages in Skype for Business Online (does not apply to Microsoft Teams). [bool]$AllowResourceAccountSendMessage, # When set to True, Supervised Chat is enabled for the tenant. [bool]$AllowRoleBasedChatPermissions, # If set to $true, the Exchange address book policy (ABP) will be used to provide customized view of the global address book for each user. This is only a virtual separation and not a legal separation. [bool]$AllowScopedPeopleSearchandAccess, # Designates whether users are able to leverage ShareFile as a third party storage solution in Microsoft Teams. If $true, users will be able to add ShareFile in the client and interact with the files stored there. [bool]$AllowShareFile, # When set to $true, Teams conversations automatically show up in Skype for Business for users that aren't enabled for Teams. [bool]$AllowSkypeBusinessInterop, # Designates whether users are able to leverage Egnyte as a third party storage solution in Microsoft Teams. If $true, users will be able to add Egnyte in the client and interact with the files stored there. [bool]$AllowEgnyte, # This setting applies only to Skype for Business Online (not Microsoft Teams) and defines whether the user must provide a secondary form of authentication to access the meeting content from a resource device account. Meeting content is defined as files that are shared to the Content Bin - files that have been attached to the meeting. [ValidateSet('NotRequired','RequiredOutsideScheduleMeeting','AlwaysRequired')] [string]$ContentPin, # TBD [bool]$ExtendedWorkInfoInPeopleSearch, # Require a secondary form of authentication to access meeting content. [ValidateSet('NoAccess','PartialAccess','FullAccess')] [string]$ResourceAccountContentAccess, # This setting controls whether users are redirected from teams.microsoft.com to the unified domain teams.cloud.microsoft. Possible values are: MicrosoftDefault, Microsoft will manage redirection behavior. If no explicit admin configuration is set, users may be redirected automatically. Disabled, Users will remain on teams.microsoft.com. Use this if your organization's apps are incompatible with the unified domain [ValidateSet('MicrosoftDefault','Disabled')] [string]$UseUnifiedDomain, # Credentials of the Teams Admin [string]$Credential, # Id of the Azure Active Directory application to authenticate with. [string]$ApplicationId, # Name of the Azure Active Directory tenant used for authentication. Format contoso.onmicrosoft.com [string]$TenantId, # Thumbprint of the Azure Active Directory application's authentication certificate to use for authentication. [string]$CertificateThumbprint, # Username can be made up to anything but password will be used for CertificatePassword [string]$CertificatePassword, # Path to certificate used in service principal usually a PFX file. [string]$CertificatePath, # Managed ID being used for authentication. [bool]$ManagedIdentity ) Invoke-KritTcmM365DscSchemaBridge -ResourceName 'TeamsClientConfiguration' -Workload 'Teams' -Verb 'Get' -CallerParams $PSBoundParameters } |