Merge branch 'main' into Office-docs-powershell-Release-Branch

Author: Ashok-Lobo

exchange/docs-conceptual/connect-exo-powershell-managed-identity.md

@@ -92,10 +92,10 @@ Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com
 After you've [created and configured a user-assigned managed identity](#create-and-configure-a-user-assigned-managed-identity), use the following syntax to connect to Exchange Online PowerShell:
 
 ```powershell
-Connect-ExchangeOnline -ManagedIdentity -Organization <YourDomain>.onmicrosoft.com -ManagedIdentityAccountId <UserAssignedManagedIdentityPrincipalIdValue>
+Connect-ExchangeOnline -ManagedIdentity -Organization <YourDomain>.onmicrosoft.com -ManagedIdentityAccountId <UserAssignedManagedIdentityClientIdValue>
 ```
 
-You get the \<UserAssignedManagedIdentityPrincipalIdValue\> value from [Step 3: Store the user-assigned managed identity in a variable](#step-3-store-the-user-assigned-managed-identity-in-a-variable).
+You get the \<UserAssignedManagedIdentityClientIdValue\> value from [Step 3: Store the user-assigned managed identity in a variable](#step-3-store-the-user-assigned-managed-identity-in-a-variable).
 
 The rest of this section explains how to connect using supported Azure resources. For example:
 
@@ -134,7 +134,7 @@ After you've successfully created the PowerShell runbook, do the following steps
 In a Windows PowerShell window in the Azure VM, use the command as described in the beginning of this section. For example:
 
 ```powershell
-$MI_ID = (Get-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2").PrincipalId
+$MI_ID = (Get-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2").ClientId
 
 Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com -ManagedIdentityAccountId $MI_ID
 ```
@@ -518,10 +518,10 @@ For instructions, see the following articles:
 
 ### Step 3: Store the user-assigned managed identity in a variable
 
-Use the following syntax in [Azure Az PowerShell](/powershell/azure/install-az-ps) to store the PrincipalId value of the user-assigned managed identity in variable that you'll use in the upcoming steps:
+Use the following syntax in [Azure Az PowerShell](/powershell/azure/install-az-ps) to store the ClientId value of the user-assigned managed identity in variable that you'll use in the upcoming steps:
 
 ```powershell
-$MI_ID = (Get-AzUserAssignedIdentity -Name "<UserAssignedMI>" -ResourceGroupName "<MIResourceGroupName>").PrincipalId
+$MI_ID = (Get-AzUserAssignedIdentity -Name "<UserAssignedMI>" -ResourceGroupName "<MIResourceGroupName>").ClientId
 ```
 
 - \<UserAssignedMI\> is the name of the user-assigned managed identity.
@@ -530,7 +530,7 @@ $MI_ID = (Get-AzUserAssignedIdentity -Name "<UserAssignedMI>" -ResourceGroupName
 For example:
 
 ```powershell
-$MI_ID = (Get-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2").PrincipalId
+$MI_ID = (Get-AzUserAssignedIdentity -Name "ContosoMI1" -ResourceGroupName "ContosoRG2").ClientId
 ```
 
 To verify that the variable was captured successfully, run the command `$MI_ID`. The output should be a GUID value (for example, bf6dcc76-4331-4942-8d50-87ea41d6e8a1).

exchange/exchange-ps/exchange/Enable-DistributionGroup.md

@@ -36,6 +36,8 @@ The Enable-DistributionGroup cmdlet mail-enables existing universal security gro
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not 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).
 
+In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
+
 ## EXAMPLES
 
 ### Example 1

exchange/exchange-ps/exchange/Enable-Mailbox.md

@@ -274,6 +274,8 @@ When mailbox-enabling an existing user, beware of non-supported characters in th
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not 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).
 
+In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
+
 ## EXAMPLES
 
 ### Example 1

exchange/exchange-ps/exchange/New-DistributionGroup.md

@@ -61,6 +61,8 @@ Distribution groups are used to consolidate groups of recipients into a single p
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not 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).
 
+In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
+
 ## EXAMPLES
 
 ### Example 1

exchange/exchange-ps/exchange/New-Mailbox.md

@@ -764,6 +764,8 @@ New-Mailbox [-Name] <String> [-SupervisoryReviewPolicy]
 ## DESCRIPTION
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not 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).
 
+In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
+
 ## EXAMPLES
 
 ### Example 1

exchange/exchange-ps/exchange/Remove-RecipientPermission.md

@@ -165,7 +165,7 @@ Accept wildcard characters: False
 ```
 
 ### -SkipDomainValidationForMailContact
-{{ Fill SkipDomainValidationForMailContact Description }}
+The SkipDomainValidationForMailContact switch skips the check that confirms the proxy addresses of the external contact specified by the Identity parameter are in an accepted domain of the organization. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 ```
 
 ### -SkipDomainValidationForMailUser
-{{ Fill SkipDomainValidationForMailUser Description }}
+The SkipDomainValidationForMailUser switch skips the check that confirms the proxy addresses of the mail user specified by the Identity parameter are in an accepted domain of the organization. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 ```
 
 ### -SkipDomainValidationForSharedMailbox
-{{ Fill SkipDomainValidationForSharedMailbox Description }}
+The SkipDomainValidationForSharedMailbox switch skips the check that confirms the proxy addresses of the shared mailbox specified by the Identity parameter are in an accepted domain of the organization. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter