Merge branch 'master' into updateSPOTenantParamDocs

Author: Kateyanne

exchange/docs-conceptual/exchange-online-powershell-v2.md

@@ -310,13 +310,13 @@ For detailed syntax and parameter information, see [Update-Module](/powershell/m
   - x64:
 
     ```powershell
-    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
+    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
     ```
 
   - x86
 
     ```powershell
-    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
+    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
     ```
 
   For more information, see [SchUseStrongCrypto](/dotnet/framework/network-programming/tls#schusestrongcrypto).

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

@@ -1068,7 +1068,7 @@ Accept wildcard characters: False
 ### -MicrosoftOnlineServicesID
 This parameter is available only in the cloud-based service.
 
-The MicrosoftOnlineServicesID parameter specifies the user ID for the object. This parameter only applies to objects in the cloud-based service. It isn't available for on-premises deployments.
+The MicrosoftOnlineServicesID parameter specifies the user ID for the object. This parameter applies only to objects in the cloud-based service and is used instead of the  UserPrincipalName parameter. The MicrosoftOnlineServicesID parameter isn't available in on-premises deployments.
 
 ```yaml
 Type: WindowsLiveId
@@ -1224,6 +1224,8 @@ This parameter is available only in on-premises Exchange.
 
 The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides.
 
+In the cloud-based service, use the MicrosoftOnlineServicesID parameter instead.
+
 ```yaml
 Type: String
 Parameter Sets: User, Arbitration, AuditLog, RemoteArchive

exchange/exchange-ps/exchange/New-MailboxRepairRequest.md

@@ -95,37 +95,37 @@ This example creates a variable that identifies Ann Beebe's mailbox and then use
 ### -CorruptionType
 The CorruptionType parameter specifies the type of corruption that you want to detect and repair. You can use the following values:
 
-- AbandonedMoveDestination: Exchange 2016 or later, but only with the Database parameter, not the Mailbox parameter.
-- AggregateCounts: Aggregate counts on folders that aren't reflecting correct values.
-- BigFunnelMissingPOIs: Exchange 2016.
+- AbandonedMoveDestination\*: Exchange 2016 or later, but only with the Database parameter, not the Mailbox parameter.
+- AggregateCounts\*: Aggregate counts on folders that aren't reflecting correct values.
+- BigFunnelMissingPOIs\*: Exchange 2016.
 - BigFunnelPOI: Exchange 2019.
-- CleanupFilesFolder: Exchange 2016 or later.
-- CleanupGraphNodesWithPropertyError: Exchange 2016 or later.
-- CleanupOfficeGraphFolders: Exchange 2016 or later.
+- CleanupFilesFolder\*: Exchange 2016 or later.
+- CleanupGraphNodesWithPropertyError\*: Exchange 2016 or later.
+- CleanupOfficeGraphFolders\*: Exchange 2016 or later.
 - CleanupOfficeGraphSsc: Exchange 2016 or later.
-- CleanupOrphanedIndexes: Exchange 2016 or later.
-- CleanupTrendingAroundMe: Exchange 2016 or later.
-- CorruptJunkRule: Exchange 2013 or later.
-- CorruptSearchFolderCriteria: Exchange 2016 or later.
-- CorruptedPerUserData: Exchange 2016 or later.
-- DropAllLazyIndexes: Exchange 2013 or later.
-- EmptyFilesFolder: Exchange 2016 or later.
+- CleanupOrphanedIndexes\*: Exchange 2016 or later.
+- CleanupTrendingAroundMe\*: Exchange 2016 or later.
+- CorruptJunkRule\*: Exchange 2013 or later.
+- CorruptSearchFolderCriteria\*: Exchange 2016 or later.
+- CorruptedPerUserData\*: Exchange 2016 or later.
+- DropAllLazyIndexes\*: Exchange 2013 or later.
+- EmptyFilesFolder\*: Exchange 2016 or later.
 - Extension1: Exchange 2013 or later, but reserved for internal Microsoft use.
 - Extension2: Exchange 2013 or later, but reserved for internal Microsoft use.
 - Extension3: Exchange 2013 or later, but reserved for internal Microsoft use.
 - Extension4: Exchange 2013 or later, but reserved for internal Microsoft use.
 - Extension5: Exchange 2013 or later, but reserved for internal Microsoft use.
-- FocusedInboxCleanup: Exchange 2016 or later.
-- FolderACL: Exchange 2013 or later.
-- FolderView: Views on folders that aren't returning correct contents.
-- ImapId: Exchange 2013 or later.
-- LockedMoveTarget: Exchange 2013 or later, but only if the mailbox is locked.
+- FocusedInboxCleanup\*: Exchange 2016 or later.
+- FolderACL\*: Exchange 2013 or later.
+- FolderView\*: Views on folders that aren't returning correct contents.
+- ImapId\*: Exchange 2013 or later.
+- LockedMoveTarget\*: Exchange 2013 or later, but only if the mailbox is locked.
 - MessageId
 - MessagePtagCn
 - MissingSpecialFolders: Exchange 2013 or later.
 - OlcFolderCleanup: Exchange 2016 or later.
 - ProvisionedFolder: Provisioned folders that are incorrectly pointing into parent folders that aren't provisioned.
-- ReduceRedundantAI: Exchange 2016 or later, and only by itself.
+- ReduceRedundantAI\*: Exchange 2016 or later.
 - RemovePICWFolder: Exchange 2016 or later, but reserved for internal Microsoft use.
 - ReplState: Exchange 2013 or later.
 - RestrictionFolder: Exchange 2013 or later.
@@ -137,6 +137,8 @@ The CorruptionType parameter specifies the type of corruption that you want to d
 
 You can specify multiple values separated by commas.
 
+\* You can only use this value by itself.
+
 ```yaml
 Type: MailboxStoreCorruptionType[]
 Parameter Sets: (All)

exchange/exchange-ps/exchange/New-MigrationBatch.md

@@ -57,6 +57,7 @@ New-MigrationBatch -Name <String> [-CSVData <Byte[]>] [-DisallowExistingUsers] [
  [-SkipMerging <MultiValuedProperty>]
  [-SkipMoving <MultiValuedProperty>]
  [-SkipReports]
+ [-SkipRules]
  [-SkipSteps <SkippableMigrationSteps[]>]
  [-SourceEndpoint <MigrationEndpointIdParameter>]
  [-SourcePFPrimaryMailboxGuid <Guid>]
@@ -959,6 +960,7 @@ Folder names aren't case-sensitive, and there are no character restrictions. Use
 If the user creates a personal folder with the same name as a well-known folder and the `#` symbol surrounding it, you can use a backslash (`\`) as an escape character to specify that folder. For example, if a user creates a folder named `#Notes#` and you want to specify that folder instead of the well-known Notes folder, use the following syntax: `\#Notes\#`.
 
 Wildcard characters can't be used in folder names.
+
 ```yaml
 Type: MultiValuedProperty
 Parameter Sets: Onboarding
@@ -1269,6 +1271,24 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -SkipRules
+This parameter is available only in the cloud-based service.
+
+The SkipRules switch specifies that you want to skip rule migration during GSuite onboarding. You don't need to specify a value with this switch.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: Onboarding
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -SkipSteps
 This parameter is available only in on-premises Exchange.
 

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteRenameState.md

@@ -24,6 +24,12 @@ Returns the current rename job state of a SharePoint Online Site.
 Get-SPOSiteRenameState -Identity <SpoSitePipeBind> [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
+### ParentId
+
+```powershell
+Get-SPOSiteRenameState -ParentOperationId <guid> [-State <RenameState>] [-WhatIf] [-Confirm] [<CommonParameters>]
+```
+
 ### RenameReport
 
 ```powershell
@@ -52,6 +58,15 @@ Get-SPOSiteRenameState -State InProgress
 
 This example returns rename jobs that are in InProgress state.
 
+### Example 3
+
+```powershell
+$tenantRenameJobId = (Get-SPOTenantRenameStatus).RenameJobId
+Get-SPOSiteRenameState -ParentOperationId $tenantRenameJob
+```
+
+This example returns rename jobs that were initiated by a tenant rename.
+
 ## PARAMETERS
 
 ### -Identity
@@ -70,15 +85,35 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ParentOperationId
+
+The parent operation id that initiated the site to be renamed. For example, the tenant rename job id.
+
+```yaml
+Type: guid
+Parameter Sets: ParentId
+Aliases:
+Applicable: SharePoint Online
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -State
 
 The state of the rename job, possible values are
 
-- Success
+- Queued
 
 - InProgress
 
-- Fail
+- Success
+
+- Failed
+
+- Suspended
 
 ```yaml
 Type: RenameState

skype/skype-ps/skype/New-CsDiagnosticsFilter.md

@@ -26,6 +26,7 @@ This cmdlet was introduced in Lync Server 2010.
 New-CsDiagnosticsFilter [-Enabled <Boolean>] [-ExcludeConferenceMessages <Boolean>]
  [-ExcludePresenceNotifications <Boolean>] [-ExcludeRegisterMessages <Boolean>] [-Fqdn <PSListModifier>]
  [-Uri <PSListModifier>] [-ExcludeSubscribeMessages <Boolean>] [-ExcludeSuccessfulRequests <Boolean>]
+ [-ExcludeMidDialogRequests <Boolean>] [-ExcludeTypingNotifications <Boolean>]
  [<CommonParameters>]
 ```
 
@@ -53,7 +54,7 @@ After creating one of these virtual filters, you will then need to use either th
 ## EXAMPLES
 
 
-### -------------------------- EXAMPLE 1 -------------------------- 
+### EXAMPLE 1
 ```
 $x = New-CsDiagnosticsFilter -Fqdn "fabrikam.com" -Enabled $False
 
@@ -71,7 +72,7 @@ In this case, any existing values in the Filter property will be replaced by the
 
 
 
-### -------------------------- EXAMPLE 2 -------------------------- 
+### EXAMPLE 2
 ```
 $x = New-CsDiagnosticsFilter -Fqdn "fabrikam.com","contoso.com" -Enabled $False
 
@@ -235,6 +236,36 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ExcludeMidDialogRequests
+If set to True, information about mid-dialog SIP requests will not be recorded in the log files.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExcludeTypingNotifications
+If set to True, information about typing notifications SIP messages will not be recorded in the log files.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+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/?LinkID=113216).`
 
@@ -257,5 +288,3 @@ The New-CsDiagnosticsFilter cmdlet creates new instances of the Microsoft.Rtc.Ma
 [New-CsDiagnosticConfiguration](New-CsDiagnosticConfiguration.md)
 
 [Set-CsDiagnosticConfiguration](Set-CsDiagnosticConfiguration.md)
-
-

skype/skype-ps/skype/New-CsExternalAccessPolicy.md

@@ -18,7 +18,7 @@ Enables you to create a new external access policy.
 External access policies determine whether or not your users can: 1) communicate with users who have Session Initiation Protocol (SIP) accounts with a federated organization; 2) communicate with users who have SIP accounts with a public instant messaging (IM) provider such as MSN; and, 3) access Skype for Business Server over the Internet, without having to log on to your internal network.
 This cmdlet was introduced in Lync Server 2010.
 
-
+For information about external access in Microsoft Teams, see [Manage external access in Microsoft Teams](/microsoftteams/manage-external-access) and [Teams and Skype interoperability](/microsoftteams/teams-skype-interop) for specific details.
 
 ## SYNTAX
 
@@ -166,7 +166,7 @@ The default value is False.
 Type: Boolean
 Parameter Sets: (All)
 Aliases: 
-Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Online, Skype for Business Server 2015, Skype for Business Server 2019
+Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
 
 Required: False
 Position: Named
@@ -343,4 +343,3 @@ Creates new instances of the Microsoft.Rtc.Management.WritableConfig.Policy.Exte
 
 [Set-CsExternalAccessPolicy](Set-CsExternalAccessPolicy.md)
 
-

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md

@@ -41,6 +41,13 @@ PS C:\> Set-CsTeamsCallingPolicy -Identity Global -AllowPrivateCalling $true
 
 Sets the value of the parameter AllowPrivateCalling, which controls whether or not users can leverage calling functionality in Microsoft Teams, in the global (default) tenant CallingPolicy.
 
+### Example 2
+```
+PS C:\> Set-CsTeamsCallingPolicy -Identity HRPolicy -LiveCaptionsEnabledTypeForCalling disabled
+```
+
+Sets the value of the parameter LiveCaptionsEnabledTypeForCalling, which controls whether real-time captions are available for the user in Teams calls, in a custom CallingPolicy called HRPolicy.
+
 ## PARAMETERS
 
 ### -AllowWebPSTNCalling
@@ -62,7 +69,7 @@ Accept wildcard characters: False
 Controls interop calling capabilities.
 Turning this on will allow Skype for Business users to have one-on-one calls with Teams users and vice-versa.
 
-[!NOTE] This parameter is disabled.
+Note: This parameter is disabled.
 
 ```yaml
 Type: Boolean

teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md

@@ -0,0 +1,60 @@
+---
+external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml
+Module Name: MicrosoftTeams
+title: Get-CsTeamsShiftsConnectionConnector
+author: gucsun
+ms.author: gucsun
+manager: navinth
+online version: https://docs.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionconnector
+schema: 2.0.0
+---
+
+# Get-CsTeamsShiftsConnectionConnector
+
+## SYNOPSIS
+
+**Note:** This cmdlet is currently in private preview.
+
+This cmdlet supports retrieving the available Shifts Connectors.
+
+## SYNTAX
+
+```
+Get-CsTeamsShiftsConnectionConnector [<CommonParameters>]
+```
+
+## DESCRIPTION
+
+This cmdlet shows the available list of Shifts Connectors that can be used to synchronize a third-party workforce management system with Teams and the types of data that can be synchronized.
+
+## EXAMPLES
+
+### Example 1
+```powershell
+PS C:\> Get-CsTeamsShiftsConnectionConnector
+```
+```
+Id                                   Name           SupportedScenario                                      Version         WfiSupportedScenario
+--                                   ----           -----------------                                      -------         --------------------
+6A51B888-FF44-4FEA-82E1-839401E9CD74 Blue Yonder V1 {Shift, SwapRequest, UserShiftPreferences, OpenShift…} 2020.3 - 2021.1 {SwapRequest, OpenShiftRequest, TimeOffRequest}
+```
+Get the list of Shifts Connectors available on the tenant.
+
+## 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](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
+
+[New-CsTeamsShiftsConnectionInstance](New-CsTeamsShiftsConnectionInstance.md)
+
+[Set-CsTeamsShiftsConnectionInstance](Set-CsTeamsShiftsConnectionInstance.md)
+
+[Test-CsTeamsShiftsConnectionValidate](Test-CsTeamsShiftsConnectionValidate.md)