Merge branch 'main' into patch-4

Ruchika-mittal01 · web-flow · commit beb4e20afef3 · 2025-10-22T02:52:05.000+05:30
diff --git a/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md b/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md
@@ -345,6 +345,8 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line
 
 ### [Remove-ContentFilterPhrase](Remove-ContentFilterPhrase.md)
 
+### [Remove-DkimSigningConfig](Remove-DkimSigningConfig.md)
+
 ### [Remove-EOPProtectionPolicyRule](Remove-EOPProtectionPolicyRule.md)
 
 ### [Remove-ExoPhishSimOverrideRule](Remove-ExoPhishSimOverrideRule.md)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DkimSigningConfig.md
@@ -0,0 +1,136 @@
+---
+applicable: Exchange Online, Exchange Online Protection
+author: chrisda
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+Locale: en-US
+Module Name: ExchangePowerShell
+ms.author: chrisda
+online version: https://learn.microsoft.com/powershell/module/exchangepowershell/remove-dkimsigningconfig
+schema: 2.0.0
+title: Remove-DkimSigningConfig
+---
+
+# Remove-DkimSigningConfig
+
+## SYNOPSIS
+This cmdlet is available only in the cloud-based service.
+
+Use the Remove-DkimSigningConfig cmdlet to remove the DomainKeys Identified Mail (DKIM) signing policy settings for domains in a cloud-based organization.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Remove-DkimSigningConfig [-Identity] <DkimSigningConfigIdParameter>
+ [-Confirm]
+ [-Force]
+ [-WhatIf]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Remove-DkimSigningConfig -Identity contoso.com
+```
+
+This example removes the DKIM signing policy for the contoso.com domain.
+
+## PARAMETERS
+
+### -Identity
+
+> Applicable: Exchange Online, Exchange Online Protection
+
+The Identity parameter specifies the DKIM signing policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
+
+- Name: The domain name (for example, contoso.com).
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: DkimSigningConfigIdParameter
+Parameter Sets: (All)
+Aliases:
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -Confirm
+
+> Applicable: Exchange Online, Exchange Online Protection
+
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Force
+
+> Applicable: Exchange Online, Exchange Online Protection
+
+The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
+
+You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+
+> Applicable: Exchange Online, Exchange Online Protection
+
+The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### 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](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/mapping/serviceMapping.json b/exchange/mapping/serviceMapping.json
@@ -159,6 +159,7 @@
   "Remove-BlockedConnector": "antispam-antimalware",
   "Remove-BlockedSenderAddress": "antispam-antimalware",
   "Remove-ContentFilterPhrase": "antispam-antimalware",
+  "Remove-DkimSigningConfig": "antispam-antimalware",
   "Remove-EOPProtectionPolicyRule": "antispam-antimalware",
   "Remove-ExoPhishSimOverrideRule": "antispam-antimalware",
   "Remove-ExoSecOpsOverrideRule": "antispam-antimalware",
diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Get-CsPhoneNumberAssignment.md
@@ -288,6 +288,68 @@ AssignmentBlockedUntil  :
 ```
 This example shows a way to get filtered results using tags. Tags are not case sensitive.
 
+### Example 14
+```powershell
+Get-CsPhoneNumberAssignment -TelephoneNumber +14025551234
+```
+```output
+TelephoneNumber         : +14025551234
+OperatorId              : 2b24d246-a9ee-428b-96bc-fb9d9a053c8d
+NumberType              : CallingPlan
+ActivationState         : Activated
+AssignedPstnTargetId    : 
+AssignmentCategory      : 
+Capability              : {UserAssignment}
+City                    : Omaha
+CivicAddressId          : 
+IsoCountryCode          : US
+IsoSubdivision          : Nebraska
+LocationId              : 
+LocationUpdateSupported : True
+NetworkSiteId           :
+PortInOrderStatus       :
+PstnAssignmentStatus    : Unassigned
+PstnPartnerId           : 7fc2f2eb-89aa-41d7-93de-73d015d22ff0
+PstnPartnerName         : Microsoft
+NumberSource            : Online
+ReverseNumberLookup		: {}
+Tag						: {}
+AssignmentBlockedState  : BlockedForever
+AssignmentBlockedUntil  :
+```
+This example displays information about the telephone number +1 (402) 555-1234 which has a permanent assignment block. This block prevents the number from being assigned to any other user. Admin can remove the block using [Remove-CsPhoneNumberAssignmentBlock](./remove-csphonenumberassignmentblock.md).
+
+### Example 15
+```powershell
+Get-CsPhoneNumberAssignment -TelephoneNumber +14025551234
+```
+```output
+TelephoneNumber         : +14025551234
+OperatorId              : 2b24d246-a9ee-428b-96bc-fb9d9a053c8d
+NumberType              : CallingPlan
+ActivationState         : Activated
+AssignedPstnTargetId    : 
+AssignmentCategory      : 
+Capability              : {UserAssignment}
+City                    : Omaha
+CivicAddressId          : 
+IsoCountryCode          : US
+IsoSubdivision          : Nebraska
+LocationId              : 
+LocationUpdateSupported : True
+NetworkSiteId           :
+PortInOrderStatus       :
+PstnAssignmentStatus    : Unassigned
+PstnPartnerId           : 7fc2f2eb-89aa-41d7-93de-73d015d22ff0
+PstnPartnerName         : Microsoft
+NumberSource            : Online
+ReverseNumberLookup		: {}
+Tag						: {}
+AssignmentBlockedState  : BlockedUntil
+AssignmentBlockedUntil  : 2025-10-11T21:30:00.0000000Z
+```
+This example displays information about the telephone number +1 (402) 555-1234 which has a temporary assignment block. This block prevents the number from being assigned to any other user. Once the period shown in AssignmentBlockUntil passes, the AssignmentBlock will be automatically removed and the number will become available to be assigned to any user. Admin can also remove the block manually using [Remove-CsPhoneNumberAssignmentBlock](./remove-csphonenumberassignmentblock.md).
+
 
 ## PARAMETERS
 
diff --git a/teams/teams-ps/MicrosoftTeams/New-CsInboundBlockedNumberPattern.md b/teams/teams-ps/MicrosoftTeams/New-CsInboundBlockedNumberPattern.md
@@ -20,18 +20,18 @@ Adds a blocked number pattern to the tenant list.
 
 ### Identity (Default)
 ```
-New-CsInboundBlockedNumberPattern [-Identity] <string> -Pattern <string> [-Description <string>] [-Enabled <boolean>]
+New-CsInboundBlockedNumberPattern [-Identity] <string> -Pattern <string> [-ResourceAccount <guid>] [-Description <string>] [-Enabled <boolean>]
  [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ### ParentAndRelativeKey
 ```
-New-CsInboundBlockedNumberPattern -Pattern <string> -Name <string> [-Description <string>] [-Enabled <boolean>]
+New-CsInboundBlockedNumberPattern -Pattern <string> -Name <string> [-ResourceAccount <guid>] [-Description <string>] [-Enabled <boolean>]
  [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-This cmdlet adds a blocked number pattern to the tenant list. An inbound PSTN call from a number that matches the blocked number pattern will be blocked.
+This cmdlet adds a blocked number pattern to the tenant list. An inbound PSTN call from a number that matches the blocked number pattern will be blocked. If a ResourceAccount is specified, the call will be redirected to that resource account instead of being blocked.
 
 ## EXAMPLES
 
@@ -42,6 +42,13 @@ PS> New-CsInboundBlockedNumberPattern -Description "Avoid Unwanted Automatic Cal
 
 This example adds a blocked number pattern to block inbound calls from +11234567890 number.
 
+### Example 2
+```powershell
+PS> New-CsInboundBlockedNumberPattern -Description "Avoid Unwanted Automatic Call" -Name "BlockAutomatic" -Pattern "^\+11234567890" -ResourceAccount "d290f1ee-6c54-4b01-90e6-d701748f0851"
+```
+
+This example adds a blocked number pattern to redirect inbound calls from +11234567890 number to the specified resource account instead of blocking it.
+
 ## PARAMETERS
 
 ### -Confirm
@@ -134,6 +141,21 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ResourceAccount
+The GUID of a resource account to redirect calls to when the pattern matches. If specified, matched calls will be redirected to this resource account instead of being blocked.
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.
diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsInboundBlockedNumberPattern.md b/teams/teams-ps/MicrosoftTeams/Set-CsInboundBlockedNumberPattern.md
@@ -20,7 +20,7 @@ Modifies one or more parameters of a blocked number pattern in the tenant list.
 
 ### Identity (Default)
 ```
-Set-CsInboundBlockedNumberPattern [[-Identity] <string>] [-Description <string>] [-Enabled <boolean>] [-Pattern <string>]
+Set-CsInboundBlockedNumberPattern [[-Identity] <string>] [-Description <string>] [-Enabled <boolean>] [-Pattern <string>] [-ResourceAccount <guid>]
  [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
@@ -36,6 +36,13 @@ PS> Set-CsInboundBlockedNumberPattern -Identity "BlockAutomatic" -Pattern "^\+11
 
 This example modifies a blocked number pattern to block inbound calls from +11234567890 number.
 
+### Example 2
+```powershell
+PS> Set-CsInboundBlockedNumberPattern -Identity "BlockAutomatic" -ResourceAccount "d290f1ee-6c54-4b01-90e6-d701748f0851"
+```
+
+This example modifies a blocked number pattern to redirect inbound calls from its pattern number to the specified resource account instead of blocking it.
+
 ## PARAMETERS
 
 ### -Confirm
@@ -113,6 +120,21 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ResourceAccount
+The GUID of a resource account to redirect calls to when the pattern matches. If specified, matched calls will be redirected to this resource account instead of being blocked.
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.
diff --git a/teams/teams-ps/MicrosoftTeams/Test-CsInboundBlockedNumberPattern.md b/teams/teams-ps/MicrosoftTeams/Test-CsInboundBlockedNumberPattern.md
@@ -14,6 +14,9 @@ title: Test-CsInboundBlockedNumberPattern
 
 ## SYNOPSIS
 This cmdlet tests the given number against the created (by using New-CsInboundBlockedNumberPattern cmdlet) blocked numbers pattern.
+Cmdlet will return an object with two properties:
+- IsMatch: True if the given number matches any of the blocked number patterns, otherwise False
+- ResourceAccount: If the matched blocked number pattern has a ResourceAccount assigned, it will return the ResourceAccount Guid, otherwise null.
 
 ## SYNTAX
 
@@ -109,6 +112,15 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## OUTPUTS
 
 ### System.Object
+An object with two properties:
+- IsMatch: True if the given number matches any of the blocked number patterns, otherwise False
+- ResourceAccount: If the matched blocked number pattern has a ResourceAccount assigned, it will return the ResourceAccount Guid, otherwise null.
+```
+{
+    "IsMatch": true,
+    "ResourceAccount": "00000000-0000-0000-0000-000000000000"
+}
+```
 
 ## NOTES
 
