Public/generated/Get-KritTcmEXOOutboundConnector.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-KritTcmEXOOutboundConnector { <# .SYNOPSIS Krit.TCM shim for M365DSC resource EXOOutboundConnector. .DESCRIPTION Auto-generated from M365DSC .schema.mof by scripts/m365-setup/Generate-KritTcmFromM365DscSchema.ps1 (.1507o30). Search-replace safe: callers that today invoke Get-M365DSCEXOOutboundConnector -Credential $cred -TenantId $tid can rename to Get-KritTcmEXOOutboundConnector -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: Exchange Original mof: C:\Users\joshl\OneDrive - Kritical Pty Ltd\Github\KRTPax8ToShopifyConnector\.kritm365-mine\Microsoft365DSC\Modules\Microsoft365DSC\DSCResources\MSFT_EXOOutboundConnector\MSFT_EXOOutboundConnector.schema.mof Param count: 22 Generator wave: .1507o30 #> [CmdletBinding()] param( # The Identity parameter specifies the outbound connector that you want to modify. [Parameter(Mandatory)] [string]$Identity, # Specifies whether connector is enabled. [bool]$Enabled, # Specifies whether connector should use MXRecords for target resolution. [bool]$UseMXRecord, # The Comment parameter specifies an optional comment. [string]$Comment, # The ConnectorSource parameter specifies how the connector is created. DO NOT CHANGE THIS! [ValidateSet('Default','Migrated','HybridWizard')] [string]$ConnectorSource, # The ConnectorType parameter specifies a category for the domains that are serviced by the connector. [ValidateSet('Partner','OnPremises')] [string]$ConnectorType, # The TlsDomain parameter specifies the domain name that the Outbound connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection. This parameter is only used if the TlsSettings parameter is set to DomainValidation. Valid input for the TlsDomain parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: *.contoso.com. However, you can't embed a wildcard character, as shown in the following example: domain.*.contoso.com [string]$TlsDomain, # The TlsSettings parameter specifies the TLS authentication level that's used for outbound TLS connections established by this Outbound connector. [ValidateSet('EncryptionOnly','CertificateValidation','DomainValidation')] [string]$TlsSettings, # The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). [bool]$IsTransportRuleScoped, # The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises messaging system (Centralized mailrouting). [bool]$RouteAllMessagesViaOnPremises, # The CloudServicesMailEnabled parameter specifies whether the connector is used for hybrid mail flow between an on-premises Exchange environment and Microsoft Office 365. Specifically, this parameter controls how certain internal X-MS-Exchange-Organization-* message headers are handled in messages that are sent between accepted domains in the on-premises and cloud organizations. These headers are collectively known as cross-premises headers. DO NOT USE MANUALLY! [bool]$CloudServicesMailEnabled, # The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. [bool]$AllAcceptedDomains, # The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. [bool]$SenderRewritingEnabled, # The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. [bool]$TestMode, # Specifies if this Outbound connector should exist. [ValidateSet('Present','Absent')] [string]$Ensure, # Credentials of the Exchange Global Admin [string]$Credential, # Id of the Azure Active Directory application to authenticate with. [string]$ApplicationId, # Id of the Azure Active Directory tenant used for authentication. [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 'EXOOutboundConnector' -Workload 'Exchange' -Verb 'Get' -CallerParams $PSBoundParameters } |