Merge branch 'master' into chrisda

Author: chrisda

.openpublishing.publish.config.json

@@ -265,7 +265,6 @@
       "template_folder": "_themes.pdf"
     }
   },
-  "need_generate_pdf": false,
   "need_generate_intellisense": false,
   "enable_incremental_build": false,
   "dependent_packages": [

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md

@@ -17,7 +17,7 @@ description: "Learn how to connect to Security & Compliance Center PowerShell."
 Office 365 Security & Compliance Center PowerShell allows you to manage your Office 365 Security & Compliance Center settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to the Security & Compliance Center. It's a simple three-step process where you enter your Office 365 credentials, provide the required connection settings, and then import the Security & Compliance Center cmdlets into your local Windows PowerShell session so that you can use them.
 
 > [!NOTE]
-> If you want to use multi-factor authentication (MFA) to connect to Security & Compliance Center PowerShell, or if your organization uses federated authentication, you need to download and use the Exchange Online Remote PowerShell Module. For more information, see [Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication](mfa-connect-to-scc-powershell.md). For some features (for example, mailbox archiving), the Security & Compliance Center links to existing functionality in the Exchange admin center (EAC). To use PowerShell with these features, you need to connect to Exchange Online instead of the Security & Compliance Center. For more information, see [Connect to Exchange Online PowerShell](../../exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md). 
+> The procedures in this topic won't work if: <br/>• Your account uses multi-factor authentication (MFA). <br/>• Your organization uses federated authentication. <br/>• A location condition in an Azure Active Directory conditional access policy restricts your access to trusted IPs. <br/> In these scenarions, you need to download and use the Exchange Online Remote PowerShell Module to connect to Security & Compliance Center PowerShell. For instructions, see [Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication](mfa-connect-to-scc-powershell.md). <br/><br/> Some features in the Security & Compliance Center (for example, mailbox archiving) link to existing functionality in the Exchange admin center (EAC). To use PowerShell with these features, you need to connect to Exchange Online PowerShell instead of Security & Compliance Center PowerShell. For instructions, see [Connect to Exchange Online PowerShell](../../exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md). <br/><br/> 
 
 For more information about the Security & Compliance Center, see [Office 365 Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=627054).
 
@@ -59,31 +59,31 @@ For more information about the Security & Compliance Center, see [Office 365 Sec
 
 1. On your local computer, open Windows PowerShell and run the following command:
 
-    ```
-    $UserCredential = Get-Credential
-    ```
+   ```
+   $UserCredential = Get-Credential
+   ```
 
-    In the **Windows PowerShell Credential Request** dialog box that appears, type your work or school account and password, and then click **OK**.
+   In the **Windows PowerShell Credential Request** dialog box that appears, type your work or school account and password, and then click **OK**.
 
 2. Run the following command:
 
-    ```
-    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
-    ```
+   ```
+   $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
+   ```
 
-    **Notes**:
+   **Notes**:
 
-    - For Office 365 Germany, use the _ConnectionUri_ value: `https://ps.compliance.protection.outlook.de/powershell-liveid/`.
+   - For Office 365 Germany, use the _ConnectionUri_ value: `https://ps.compliance.protection.outlook.de/powershell-liveid/`.
 
-    - For Office 365 Government Community Cloud High (GCC High), use the _ConnectionUri_ value: `https://ps.compliance.protection.office365.us/powershell-liveid/
+   - For Office 365 Government Community Cloud High (GCC High), use the _ConnectionUri_ value: `https://ps.compliance.protection.office365.us/powershell-liveid/
 
-    - If you want to connect to Security & Compliance Center PowerShell in the same window as an active Exchange Online PowerShell connection, you need to add the Prefix parameter and value (for example, `-Prefix "CC"`) to the end of this command to prevent cmdlet name collisions (both environments share some cmdlets with the same names).
+   - If you want to connect to Security & Compliance Center PowerShell in the same window as an active Exchange Online PowerShell connection, you need to add the Prefix parameter and value (for example, `-Prefix "CC"`) to the end of this command to prevent cmdlet name collisions (both environments share some cmdlets with the same names).
 
 3. Run the following command:
 
-    ```
-    Import-PSSession $Session -DisableNameChecking
-    ```
+   ```
+   Import-PSSession $Session -DisableNameChecking
+   ```
 
 > [!NOTE]
 > Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command. 
@@ -108,9 +108,9 @@ If you receive errors, check the following requirements:
 
 - The **New-PSSession** command (Step 2) might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this:
 
-    `The request for the Windows Remote Shell with ShellId <ID> failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.`
+  `The request for the Windows Remote Shell with ShellId <ID> failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.`
 
-    To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Security & Compliance Center PowerShell endpoint.
+  To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Security & Compliance Center PowerShell endpoint.
  
 ## See also
 

exchange/exchange-ps/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md

@@ -35,6 +35,7 @@ Set-AntiPhishPolicy -Identity <AntiPhishPolicyIdParameter>
  [-EnableSimilarUsersSafetyTips <$true | $false>]
  [-EnableTargetedDomainsProtection <$true | $false>]
  [-EnableTargetedUserProtection <$true | $false>]
+ [-EnableUnauthenticatedSender <$true | $false>]
  [-EnableUnusualCharactersSafetyTips <$true | $false>]
  [-ExcludedDomains <MultiValuedProperty>]
  [-ExcludedSenders <MultiValuedProperty>]
@@ -324,6 +325,25 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EnableUnauthenticatedSender
+The EnableUnauthenticatedSender parameter specifies whether to apply a "?" symbol in Outlook's sender card if the sender fails authentication checks. Valid values are:
+
+- $true: Apply the "?" symbol.
+
+- $false: Do not apply the "?" symbol.
+
+```yaml
+Type: $true | $false
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
+Required: False
+Position: Named
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -EnableUnusualCharactersSafetyTips
 The EnableUnusualCharactersSafetyTips parameter specifies whether to enable safety tips that are shown to recipients in messages for unusual characters in domain and user impersonation detections. Valid values are:
 

exchange/exchange-ps/exchange/mailboxes/Get-MailboxFolderPermission.md

@@ -44,6 +44,13 @@ Get-MailboxFolderPermission -Identity [email protected]:\Marketing\Reports -User
 
 This example returns the permissions for the same folder in John's mailbox, but only for the user Ayla.
 
+### -------------------------- Example 3 --------------------------
+```
+Get-MailboxFolderPermission -Identity [email protected]:\Calendar -User [email protected]
+```
+
+This example returns the permissions for the Calendar folder in John's mailbox, but only for the user Ayla.
+
 ## PARAMETERS
 
 ### -Identity

sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOCommSite.md

@@ -12,8 +12,12 @@ ms.reviewer:
 
 
 ## SYNOPSIS
+
 Enables the modern communication site experience on an existing site.
 
+**At this time, based on early adopter feedback, we have decided to postpone rolling out this feature. We apologize for any inconvenience and will communicate a new schedule via Message Center, once it is available. We expect to have an update in the Q3 time frame**
+
+
 
 ## SYNTAX
 
@@ -22,7 +26,7 @@ Enable-SPOCommSite [-SiteUrl] <string> [-DesignPackageId] <GUID>
 ```
 
 ## DESCRIPTION
-Use this cmdlet to enable the modern communication site experience at the classic root site of a tenant. You must use the SharePoint admin powershell version 8715.1200 or greater. Use of this cmdlet is subject to rollout of capability. At this time, based on early adopter feedback, we have decided to postpone rolling out this feature. We apologize for any inconvenience and will communicate a new schedule via Message Center, once it is available. We expect to have an update in the Q3 time frame
+Use this cmdlet to enable the modern communication site experience at the classic root site of a tenant. You must use the SharePoint admin powershell version 8715.1200 or greater. Use of this cmdlet is subject to rollout of capability.
 
 **Current limitations**
 
@@ -55,10 +59,8 @@ This example enables the communication site experience at this https://contoso.s
 
 ```
 $orgName="<tenantname>"
-$adminUPN = "<Current SharePoint Online Admin Login ID>"
 $rootSiteURL = "<Root site URL>"
-$userCredential = Get-Credential -UserName $adminUPN -Message "Type the password."
-Connect-SPOService -Url https://$orgName-admin.sharepoint.com -Credential $userCredential
+Connect-SPOService -Url https://$orgName-admin.sharepoint.com
 Enable-SPOCommSite -SiteUrl $rootSiteURL
 ```
 **STEP BY STEP INSTRUCTIONS**

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

@@ -1,14 +1,14 @@
 ---
 external help file: sharepointonline.xml
 applicable: SharePoint Online
-title: Get-SPOGeoMoveCompatibilityStatus
+title: Get-SPOGeoCrossMoveCompatibilityStatus
 schema: 2.0.0
 author: trent-green
 ms.author: trgreen
 ms.reviewer:
 ---
 
-# Get-SPOGeoMoveCompatibilityStatus
+# Get-SPOGeoCrossMoveCompatibilityStatus
 
 ## SYNOPSIS
 This cmdlet returns the compatibility status between geographic locations.
@@ -17,7 +17,7 @@ This cmdlet returns the compatibility status between geographic locations.
 ## SYNTAX
 
 ```
-Get-SPOGeoMoveCompatibilityStatus [-AllLocations <Boolean>] [<CommonParameters>]
+Get-SPOGeoCrossMoveCompatibilityStatus [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -28,37 +28,11 @@ This cmdlet returns the compatibility between sites and locations for a move in
 
 ### EXAMPLE 1
 ```powershell
-Get-SPOGeoMoveCompatibilityStatus -AllLocations $true
+Get-SPOGeoCrossMoveCompatibilityStatus
 ```
 
 Get the compatibility status for all locations.
 
-### EXAMPLE 2
-```powershell
-Get-SPOGeoMoveCompatibilityStatus -AllLocations $false
-```
-
-Get the compatibility status for the current location.
-
-
-## PARAMETERS
-
-### -AllLocations
-PARAMVALUE: $true | $false
-
-
-```yaml
-Type: Boolean
-Parameter Sets: (All)
-Aliases: 
-Applicable: SharePoint Online
-
-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).

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPCustomAction.md

@@ -46,6 +46,13 @@ Get-PnPCustomAction -Scope web
 
 Returns all custom actions for the current web object.
 
+### ------------------EXAMPLE 4------------------
+```powershell
+Get-PnPCustomAction -Identity aa66f67e-46c0-4474-8a82-42bf467d07f2 -Includes 'Id','Title','ClientSideComponentProperties'
+```
+
+Returns the custom action with the id 'aa66f67e-46c0-4474-8a82-42bf467d07f2' as well as specific properties, such as ClientSiteComponentProperties
+
 ## PARAMETERS
 
 ### -Identity
@@ -126,4 +133,4 @@ Accept pipeline input: False
 
 ## RELATED LINKS
 
-[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)
+[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)

sharepoint/sharepoint-ps/sharepoint-server/Install-SPSolution.md

@@ -56,13 +56,6 @@ This example deploys the installed SharePoint solution contoso_solution.wsp in t
 
 ### ------------------EXAMPLE 2------------------ 
 ```
-Install-SPSolution -Identity contoso_solution.wsp -GACDeployment -AddtoLatestVersion $true
-```
-
-This example deploys the installed SharePoint solution contoso_solution.wsp in the farm within the latest version directories and specifies that global assembly cache (GAC) can be deployed for the new SharePoint solution.
-
-### ------------------EXAMPLE 3------------------ 
-```
 Install-SPSolution -Identity contoso_solution.wsp -GACDeployment -CompatibilityLevel {14,15}
 ```
 

skype/skype-ps/skype/Get-CsOnlineVoicemailPolicy.md

@@ -154,4 +154,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## RELATED LINKS
 [Set-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailpolicy?view=skype-ps)
 
+[New-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoicemailpolicy?view=skype-ps)
+
+[Remove-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoicemailpolicy?view=skype-ps)
+
 [Grant-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/grant-csonlinevoicemailpolicy?view=skype-ps)

skype/skype-ps/skype/Get-CsOnlineVoicemailUserSettings.md

@@ -22,9 +22,6 @@ Get-CsOnlineVoicemailUserSettings -Identity <String> [-Tenant <Guid>] [<CommonPa
 ## DESCRIPTION
 The Get-CsOnlineVoicemailUserSettings cmdlet returns information about online voicemail user settings of a specific user in your organization.
 
-**NOTE** 
-- **This cmdlet is currently available to PREVIEW customers only.** 
-
 ## EXAMPLES
 
 ### -------------------------- Example 1 --------------------------

skype/skype-ps/skype/Grant-CsOnlineVoicemailPolicy.md

@@ -11,7 +11,7 @@ ms.reviewer:
 # Grant-CsOnlineVoicemailPolicy
 
 ## SYNOPSIS
-Provide the topic introduction here.
+Assigns a online voice mail policy at the per-user scope. Online voicemail policies manage usages for Voicemail service.
 
 ## SYNTAX
 
@@ -21,25 +21,25 @@ Grant-CsOnlineVoicemailPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainCo
 ```
 
 ## DESCRIPTION
-Provide the detailed description here.
+This cmdlet assigns an existing user-specific online voicemail policy to a user. Online voicemail policies are used by the organization to manage Voicemail-related features such as transcription.
 
 ## EXAMPLES
 
-### -------------------------- Example 1 -------------------------- (Skype for Business Online)
+### -------------------------- Example 1 --------------------------
 ```
-Insert example commands for example 1.
+Grant-CsOnlineVoicemailPolicy -Identity "sip:[email protected]" -PolicyName TranscriptionDisabled
 ```
 
-Insert descriptive text for example 1.
+The command shown in Example 1 assigns the per-user online voicemail policy TranscriptionDisabled to a single user with SIP URI sip:user@contoso.com.
 
 
 ## PARAMETERS
 
 ### -Identity
-PARAMVALUE: UserIdParameter
+The Identity parameter represents the ID of the specific user in your organization; this can be either a SIP URI or an Object ID.
 
 ```yaml
-Type: UserIdParameter
+Type: System.String
 Parameter Sets: (All)
 Aliases: 
 Applicable: Skype for Business Online
@@ -52,7 +52,7 @@ Accept wildcard characters: False
 ```
 
 ### -PolicyName
-PARAMVALUE: String
+A unique identifier(name) of the policy.
 
 ```yaml
 Type: String
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 ```
 
 ### -Confirm
-PARAMVALUE: SwitchParameter
+Prompts you for confirmation before executing the command.
 
 ```yaml
 Type: SwitchParameter
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 ```
 
 ### -DomainController
-PARAMVALUE: Fqdn
+Enables you to specify the fully qualified domain name (FQDN) of a domain controller to be contacted when assigning the new policy. If this parameter is not specified then the Grant-CsMobilityPolicy cmdlet will contact the first available domain controller.
 
 ```yaml
 Type: Fqdn
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 ```
 
 ### -PassThru
-PARAMVALUE: SwitchParameter
+Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsOnlineVoicemailPolicy cmdlet does not pass objects through the pipeline.
 
 ```yaml
 Type: SwitchParameter
@@ -116,7 +116,9 @@ Accept wildcard characters: False
 ```
 
 ### -Tenant
-PARAMVALUE: Guid
+Globally unique identifier (GUID) of the Skype for Business Online tenant account whose voicemail policy is to be retrieved. For example: -Tenant "38aad667-af54-4397-aaa7-e94c79ec2308" You can return the tenant ID for each of your tenants by running this command: 
+
+`Get-CsTenant | Select-Object DisplayName, TenantID`
 
 ```yaml
 Type: Guid
@@ -132,7 +134,7 @@ Accept wildcard characters: False
 ```
 
 ### -WhatIf
-PARAMVALUE: SwitchParameter
+Describes what would happen if you executed the command without actually executing the command.
 
 ```yaml
 Type: SwitchParameter
@@ -148,7 +150,11 @@ Accept wildcard characters: False
 ```
 
 ### -AsJob
-{{Fill AsJob Description}}
+Indicates that this cmdlet runs as a background job.
+
+When you specify the AsJob parameter, the command immediately returns an object that represents the background job. You can continue to work in the session while the job finishes. The job is created on the local computer and the results from the Skype for Business Online session are automatically returned to the local computer. To get the job results, use the Receive-Job cmdlet.
+
+For more information about Windows PowerShell background jobs, see [about_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_jobs?view=powershell-6) and [about_Remote_Jobs](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_jobs?view=powershell-6).
 
 ```yaml
 Type: SwitchParameter
@@ -173,5 +179,10 @@ This cmdlet supports the common parameters: `-Debug, -ErrorAction, -ErrorVariabl
 ## NOTES
 
 ## RELATED LINKS
+[Get-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/get-csonlinevoicemailpolicy?view=skype-ps)
+
+[Set-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/set-csonlinevoicemailpolicy?view=skype-ps)
 
+[New-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/new-csonlinevoicemailpolicy?view=skype-ps)
 
+[Remove-CsOnlineVoicemailPolicy](https://docs.microsoft.com/powershell/module/skype/remove-csonlinevoicemailpolicy?view=skype-ps)