Merge branch 'main' into ICFSA-chrisda

Author: chrisda

exchange/docs-conceptual/client-advanced-settings.md

@@ -429,7 +429,7 @@ To ensure that the NTFS owner value is preserved, set the *UseCopyAndPreserveNTF
 > [!CAUTION]
 > For the scanner: Define this advanced setting only when you can ensure a low-latency, reliable network connection between the scanner and the scanned repository. A network failure during the automatic labeling process can cause the file to be lost.
 
-Example PowerShell command, where your label policy is named "Scanner"
+Example PowerShell command, where your label policy is named "Global"
 
 ```PowerShell
 Set-LabelPolicy -Identity Global -AdvancedSettings @{UseCopyAndPreserveNTFSOwner ="true"}

exchange/exchange-ps/exchange/New-DlpComplianceRule.md

@@ -680,7 +680,12 @@ Accept wildcard characters: False
 ```
 
 ### -ContentIsNotLabeled
-{{ Fill ContentIsNotLabeled Description }}
+The ContentIsNotLabeled parameter specifies a condition for the DLP rule that looks for attachments or documents that aren't labeled. Valid values are:
+
+- $true: Look for attachments or documents that aren't labeled.
+- $false: Don't look for unlabeled attachments or documents.
+
+In Exchange, this condition is matched only if both the attachment and the message body aren't labeled.
 
 ```yaml
 Type: Boolean
@@ -696,7 +701,12 @@ Accept wildcard characters: False
 ```
 
 ### -ContentIsShared
-{{ Fill ContentIsShared Description }}
+The ContentIsNotLabeled parameter specifies a condition for the DLP rule that looks for attachments or documents that aren't labeled. Valid values are:
+
+- $true: Look for attachments or documents that aren't labeled.
+- $false: Don't look for unlabeled attachments or documents.
+
+In Exchange, this condition is matched only if both the attachment and the message body aren't labeled.
 
 ```yaml
 Type: Boolean
@@ -769,7 +779,9 @@ Accept wildcard characters: False
 ```
 
 ### -DocumentCreatedBy
-{{ Fill DocumentCreatedBy Description }}
+The DocumentCreatedBy parameter specifies a condition for the DLP rule that looks for documents that are created by the specificed identity. You can specify multiple values separated by commas.
+
+This parameter applies to Sharepoint and Onedrive workloads.
 
 ```yaml
 Type: MultiValuedProperty
@@ -785,7 +797,9 @@ Accept wildcard characters: False
 ```
 
 ### -DocumentCreatedByMemberOf
-{{ Fill DocumentCreatedByMemberOf Description }}
+The DocumentCreatedByMemberOf parameter specifies a condition for the DLP rule that looks for documents that are created by a member of the specificed group. You can specify multiple values separated by commas.
+
+This parameter applies to Sharepoint and Onedrive workloads.
 
 ```yaml
 Type: RecipientIdParameter[]
@@ -1182,7 +1196,12 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfContentIsShared
-{{ Fill ExceptIfContentIsShared Description }}
+The ContentIsNotLabeled parameter specifies an exception for the DLP rule that looks for attachments or documents that aren't labeled. Valid values are:
+
+- $true: Look for attachments or documents that aren't labeled.
+- $false: Don't look for unlabeled attachments or documents.
+
+In Exchange, this condition is matched only if both the attachment and the message body aren't labeled.
 
 ```yaml
 Type: Boolean
@@ -1236,7 +1255,9 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfDocumentCreatedBy
-{{ Fill ExceptIfDocumentCreatedBy Description }}
+The DocumentCreatedBy parameter specifies an exception for the DLP rule that looks for documents that are created by the specificed identity. You can specify multiple values separated by commas.
+
+This parameter applies to Sharepoint and Onedrive workloads.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1252,7 +1273,9 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfDocumentCreatedByMemberOf
-{{ Fill ExceptIfDocumentCreatedByMemberOf Description }}
+The DocumentCreatedByMemberOf parameter specifies an exception for the DLP rule that looks for documents that are created by a member of the specificed group. You can specify multiple values separated by commas.
+
+This parameter applies to Sharepoint and Onedrive workloads.
 
 ```yaml
 Type: RecipientIdParameter[]
@@ -3285,7 +3308,13 @@ Accept wildcard characters: False
 ```
 
 ### -SharedByIRMUserRisk
-{{ Fill SharedByIRMUserRisk Description }}
+The SharedByIRMUserRisk paramter specifies the risk category of the user performing the violating action. Valid values are:
+
+- Elevated Risk Level
+- Moderate Risk Level
+- Minor Risk Level
+
+You can specify multiple values separated by commas.
 
 ```yaml
 Type: MultiValuedProperty

exchange/exchange-ps/exchange/New-InboundConnector.md

@@ -92,7 +92,7 @@ Accept wildcard characters: False
 ```
 
 ### -SenderDomains
-The SenderDomains parameter specifies the source domains that the connector accepts messages for. A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, \*.contoso.com), but you can't embed the wildcard character (for example, domain.\*.contoso.com is not valid).
+The SenderDomains parameter specifies the source domains that a Partner type connector accepts messages for (limits the scope of a Partner type connector). A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, `*.contoso.com`). However, you can't embed the wildcard character (for example, `domain.*.contoso.com` isn't valid).
 
 You can specify multiple domains separated by commas.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 The ConnectorType parameter specifies the category for the source domains that the connector accepts messages for. Valid values are:
 
 - Partner: External partners or services.
-- OnPremises: Your on-premises email organization. Use this value for accepted domains in your cloud-based organization that are also specified by the SenderDomains parameter.
+- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors grant special rights to an email that matches the connector and additional requirements. For example: allowing relay through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows.
 
 ```yaml
 Type: TenantConnectorType
@@ -353,11 +353,13 @@ Accept wildcard characters: False
 ```
 
 ### -RequireTls
-The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by the connector. Valid values are:
+The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are:
 
 - $true: Reject messages if they aren't sent over TLS. This is the default value
 - $false: Allow messages if they aren't sent over TLS.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -372,11 +374,13 @@ Accept wildcard characters: False
 ```
 
 ### -RestrictDomainsToCertificate
-The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the connector. Valid values are:
+The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are:
 
 - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
 - $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -391,11 +395,13 @@ Accept wildcard characters: False
 ```
 
 ### -RestrictDomainsToIPAddresses
-The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses. Valid values are:
+The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are:
 
 - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
 - $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -426,7 +432,7 @@ Accept wildcard characters: False
 ```
 
 ### -SenderIPAddresses
-The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the connector accepts messages from. Valid values are:
+The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the Partner type connector accepts messages from when the value of the RestrictDomainsToIPAddresses parameter is $true. Valid values are:
 
 - Single IP address: For example, 192.168.1.1.
 - Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32.
@@ -435,6 +441,8 @@ You can specify multiple IP addresses separated by commas.
 
 IPv6 addresses are not supported.
 
+**Note**: This parameter applies to Partner type connectors only if the value of the RestrictDomainsToIPAddresses parameter is $true.
+
 ```yaml
 Type: MultiValuedProperty
 Parameter Sets: (All)

exchange/exchange-ps/exchange/Set-InboundConnector.md

@@ -186,7 +186,7 @@ Accept wildcard characters: False
 The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid input for this parameter includes the following values:
 
 - Partner: The connector services domains that are external to your organization.
-- OnPremises: The connector services domains that are used by your on-premises organization. Use this value for accepted domains in your cloud-based organization that are also specified by the SenderDomains parameter.
+- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors grant special rights to an email that matches the connector and additional requirements. For example: allowing relay through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows.
 
 ```yaml
 Type: TenantConnectorType
@@ -328,11 +328,13 @@ Accept wildcard characters: False
 ```
 
 ### -RequireTls
-The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by the connector. Valid values are:
+The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are:
 
 - $true: Reject messages if they aren't sent over TLS. This is the default value
 - $false: Allow messages if they aren't sent over TLS.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -347,11 +349,13 @@ Accept wildcard characters: False
 ```
 
 ### -RestrictDomainsToCertificate
-The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the connector. Valid values are:
+The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are:
 
 - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
 - $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -366,11 +370,13 @@ Accept wildcard characters: False
 ```
 
 ### -RestrictDomainsToIPAddresses
-The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses. Valid values are:
+The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are:
 
 - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
 - $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -401,7 +407,7 @@ Accept wildcard characters: False
 ```
 
 ### -SenderDomains
-The SenderDomains parameter specifies the source domains that the connector accepts messages for. A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, \*.contoso.com), but you can't embed the wildcard character (for example, domain.\*.contoso.com is not valid).
+The SenderDomains parameter specifies the source domains that a Partner type connector accepts messages for (limits the scope of a Partner type connector). A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, `*.contoso.com`). However, you can't embed the wildcard character (for example, `domain.*.contoso.com` isn't valid).
 
 You can specify multiple domains separated by commas.
 
@@ -419,12 +425,15 @@ Accept wildcard characters: False
 ```
 
 ### -SenderIPAddresses
-The SenderIPAddresses parameter specifies the remote IPV4 IP addresses from which this connector accepts messages. IPv6 addresses are not supported. Valid values are:
+The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the Partner type connector accepts messages from when the value of the RestrictDomainsToIPAddresses parameter is $true. Valid values are:
 
 - Single IP address: For example, 192.168.1.1.
 - Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32.
+@@ -435,6 +441,8 @@ You can specify multiple IP addresses separated by commas.
 
-You can specify multiple values separated by commas.
+IPv6 addresses are not supported.
+
+**Note**: This parameter applies to Partner type connectors only if the value of the RestrictDomainsToIPAddresses parameter is $true.
 
 ```yaml
 Type: MultiValuedProperty

teams/teams-ps/teams/Get-CsSdgBulkSignInRequestsSummary.md

@@ -0,0 +1,48 @@
+---
+external help file: MicrosoftTeams-help.xml
+Module Name: MicrosoftTeams
+applicable: Microsoft Teams
+online version:
+title: Get-CsSdgBulkSignInRequestsSummary
+schema: 2.0.0
+---
+
+# Get-CsSdgBulkSignInRequestsSummary
+
+## SYNOPSIS
+Get the tenant level summary of all bulk sign in requests executed in the past 30 days.
+
+## SYNTAX
+
+```
+Get-CsSdgBulkSignInRequestsSummary [<CommonParameters>]
+```
+
+## DESCRIPTION
+This cmdlet gives the overall tenant level summary of all bulk sign in requests executed for a particular tenant within the last 30 days. Status is shown at batch level as succeeded / failed.
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Get-CsSdgBulkSignInRequestsSummary
+```
+
+This example shows how to run the cmdlet to get a tenant level summary.
+
+## PARAMETERS
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### None
+
+## OUTPUTS
+
+### Microsoft.Teams.ConfigAPI.Cmdlets.Generated.Models.ISdgBulkSignInRequestsSummaryResponseItem
+
+## NOTES
+
+## RELATED LINKS