Merge pull request #2 from MicrosoftDocs/master

merge master

Author: CHILIU-MSFT

.gitignore

@@ -7,3 +7,6 @@ _themes*/
 .local/
 
 .openpublishing.buildcore.ps1
+**/node_modules
+
+\.idea/

README.md

@@ -1,35 +1,36 @@
-# Short URL: aka.ms/office-powershell
+**Short URL: aka.ms/office-powershell**
 
 # Overview
-A repository to hold the help reference content for Office PowerShell cmdlets. The expert knowledge around Office PowerShell is distributed among customers, MVPs, partners, product teams, support, and other community members. Consumers also have various preferences when consuming knowledge such as a website, PowerShell Get-Help, Windows app, iOS app, Android app, and others. The following diagram illustrates the point.
+This repository holds reference content of Office PowerShell cmdlets for help purpose. The expert knowledge around Office PowerShell is distributed among customers, MVPs, partners, product teams, support, and other community members. Consumers have various preferences when consuming knowledge such as a website, PowerShell Get-Help, Windows app, iOS app, Android app, and others. The following diagram illustrates the point.
+
 ![Contribution and Consumption model for Office PowerShell reference content](images/contrib-consumption-model.png)
 
-# Learn How To Contribute
+## Learn How To Contribute
 Anyone who is interested can contribute to the Microsoft Office PowerShell reference topics.
-When you contribute your work will go directly into the Microsoft Office products and show up in Get-Help for the given Office cmdlet.
+Your contributions will go directly into the Microsoft Office products and show up in Get-Help for the given Office cmdlet.
 
 > Notice that if you are looking into contributing for the **PnP PowerShell cmdlets**, their documentation is automatically generated from the code, and you should be submitting your change towards the original code at https://github.com/SharePoint/PnP-powershell. See, for example, how the attributes are used in the code for the [Get-PnPList](https://github.com/SharePoint/PnP-PowerShell/blob/master/Commands/Lists/GetList.cs) cmdlet.
 
-# Quick Start
+## Quick Start
 
-## Contribute using the GitHub website
+### Contribute using the GitHub website
 
 [![Image of Quick Start video](images/edit_video_capture.jpg)](https://support.office.com/en-us/article/edit-powershell-cmdlet-in-github-dcd20227-3764-48ce-ad6e-763af8b48daf?ui=en-US&rs=en-US&ad=US)
 
-1. Open your browser, log in to GitHub, and then navigate to https://github.com/microsoftdocs/office-docs-powershell
+1. Open your browser, log in to GitHub, and navigate to https://github.com/microsoftdocs/office-docs-powershell
 2. Browse to the file you want to edit. In this example, we will edit https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/teams/teams-ps/teams/New-Team.md and add a link in the Related Links section.
 3. Click the Edit icon which looks like a pencil in the upper right corner. 
 ![Image of Edit button on Github](images/edit_icon.png)
 
-4. Your browser will then open the file in an edit window. We want to add a link. So we scroll down to the Related Links section and add the link in the correct format.
+4. Your browser will open the file in an edit window. To add a link, we scroll down to the Related Links section and add the link in the correct format.
 ![Image of Edit button on Github](images/add_related_link.png)
 
-**Note** Since you are likely not a maintainer of the Git repository, GitHub will automatically 'Fork' the project into your personal GitHub account. A fork is just an exact copy of the repository in your own account so that you have total access to make edits. You are now 'editing' a copy of the project in your own GitHub account. You can always find it again by looking at your GitHub Repositories in your GitHub Profile (drop-down from your name in the top right).
+**Note** Since you are likely not a maintainer of the Git repository, GitHub will automatically 'Fork' the project into your personal GitHub account. A fork is a copy of the repository in your git account. By forking, you can freely make edits without affecting the original repository. You can always find it again by looking at your GitHub Repositories in your GitHub Profile (drop-down from your name in the top right).
 ![Image of Automatic Fork message on Github](images/auto_fork.png)
 
 5. You can click the Preview changes link to see what the changes will look like.
 
-   **IMPORTANT** The layout of headings and subheadings must follow a very specific schema that is required for PowerShell Get-Help.
+   **IMPORTANT** The layout of headings and subheadings must follow a schema required for PowerShell Get-Help.
    Any deviation will throw errors in the Pull Request. The schema can be found here: https://github.com/PowerShell/platyPS/blob/master/platyPS.schema.md 
 
 6. Once you are satisfied with your work, go to the **Propose file change** area at the bottom of the topic. Enter a title and other description information, and then click **Propose file change**.
@@ -42,9 +43,9 @@ Looking for more in-depth content? Check out the following:
 * [Using more advanced tools with the PowerShell GitHub repo](repo_docs/ADVANCED.md)
 * [Creating content for brand new cmdlets](repo_docs/NEW_CMDLETS.md)
 
-# Microsoft Open Source Code of Conduct
+## Microsoft Open Source Code of Conduct
 
-## Contributing
+### Contributing
 
 This project welcomes contributions and suggestions. Most contributions require you to agree to a
 Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us

exchange/docfx.json

@@ -67,7 +67,7 @@
     },
     "fileMetadata": {
       "apiPlatform":{
-        "exchange-ps/exchange" : [ "PowerShell" ]
+        "exchange-ps/exchange/**/*.md" : [ "powershell" ]
       }
     },
     "template": [],

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md

@@ -11,6 +11,7 @@ localization_priority: Priority
 ms.collection: Strat_EX_Admin
 ms.custom: 
 ms.assetid: c8bea338-6c1a-4bdf-8de0-7895d427ee5b
+search.appverid: MET150
 description: "Learn how to use remote PowerShell to connect to Exchange Online."
 ---
 
@@ -46,9 +47,9 @@ Exchange Online PowerShell allows you to manage your Exchange Online settings fr
 
   To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
 
-    ```
-    Set-ExecutionPolicy RemoteSigned
-    ```
+  ```
+  Set-ExecutionPolicy RemoteSigned
+  ```
 
   You need to configure this setting only once on your computer, not every time you connect.
 
@@ -59,9 +60,10 @@ Exchange Online PowerShell allows you to manage your Exchange Online settings fr
 
 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, type your work or school account and password, and then click **OK**.
 
 2. Run the following command.
@@ -70,23 +72,25 @@ Exchange Online PowerShell allows you to manage your Exchange Online settings fr
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
    ```
 
-    **Notes**:
+   **Notes**:
 
-    - For Office 365 operated by 21Vianet, use the _ConnectionUri_ value: `https://partner.outlook.cn/PowerShell`
+   - For Office 365 operated by 21Vianet, use the _ConnectionUri_ value: `https://partner.outlook.cn/PowerShell`
 
-    - For Office 365 Germany, use the _ConnectionUri_ value: `https://outlook.office.de/powershell-liveid/`
+   - For Office 365 Germany, use the _ConnectionUri_ value: `https://outlook.office.de/powershell-liveid/`
 
-    - If you're behind a proxy server, run this command first: `$ProxyOptions = New-PSSessionOption -ProxyAccessType `, where the _ProxyAccessType_ value is `IEConfig`, `WinHttpConfig`, or `AutoDetect`.
+   - For Office 365 Government Community Cloud High (GCC High), use the _ConnectionUri_ value: `https://outlook.office365.us/powershell-liveid/`
+
+   - If you're behind a proxy server, run this command first: `$ProxyOptions = New-PSSessionOption -ProxyAccessType `, where the _ProxyAccessType_ value is `IEConfig`, `WinHttpConfig`, or `AutoDetect`.
 
-      Then, add the following parameter and value to the end of the $Session = ... command: `-SessionOption $ProxyOptions`.
+     Then, add the following parameter and value to the end of the $Session = ... command: `-SessionOption $ProxyOptions`.
 
-      For more information, see [New-PSSessionOption](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/new-pssessionoption).
+     For more information, see [New-PSSessionOption](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/new-pssessionoption).
 
 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. 
@@ -107,7 +111,7 @@ If you receive errors, check the following requirements:
 
 - The account you use to connect to Exchange Online must be enabled for remote PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](../disable-access-to-exchange-online-powershell.md).
 
-- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy.
+- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive internet access policy.
 
 ## See also
 
@@ -123,4 +127,4 @@ The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more
 
 - [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623)
 
-
+For more information about managing Office 365, see [Manage Office 365](https://docs.microsoft.com/Office365/).

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md

@@ -8,14 +8,15 @@ ms.topic: article
 ms.service: exchange-online
 localization_priority: Normal
 ms.assetid: 04dae4ce-34a7-49c5-bf75-11e72452e04a
+search.appverid: MET150
 description: "Learn how to connect to Exchange Online PowerShell by using multi-factor authentication (MFA)."
 ---
 
 # Connect to Exchange Online PowerShell using multi-factor authentication
 If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you can't use the instructions at [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md) to use remote PowerShell to connect to Exchange Online. MFA requires you to install the Exchange Online Remote PowerShell Module, and use the **Connect-EXOPSSession** cmdlet to connect.
 
 > [!NOTE]
-> You can't use the Exchange Online Remote PowerShell Module to connect to Exchange Online PowerShell and Security & Compliance Center PowerShell in the same session (window). You need to use separate sessions of the Exchange Online Remote PowerShell Module. 
+> • You can't use the Exchange Online Remote PowerShell Module to connect to Exchange Online PowerShell and Security & Compliance Center PowerShell in the same session (window). You need to use separate sessions of the Exchange Online Remote PowerShell Module. <br/>• Delegated Access Permission (DAP) partners can't use the procedures in this topic to connect to their customer tenant organizations in Exchange Online PowerShell. MFA and the Exchange Online Remote PowerShell Module don't work with delegated authentication.
 
 ## What do you need to know before you begin?
 
@@ -39,7 +40,9 @@ If you want to use multi-factor authentication (MFA) to connect to Exchange Onli
 
 - The Exchange Online Remote PowerShell Module needs to be installed on your computer:
 
-  1. In Internet Explorer or Edge, open the Exchange admin center (EAC) for your Exchange Online organization (Google Chrome or Mozilla Firefox won't work). For instructions, see [Exchange Admin Center in Exchange Online](http://technet.microsoft.com/library/ace44f6b-4084-4f9c-89b3-e0317962472b.aspx).
+  1. In Internet Explorer or Edge, open the Exchange admin center (EAC) for your Exchange Online organization. For instructions, see [Exchange Admin Center in Exchange Online](http://technet.microsoft.com/library/ace44f6b-4084-4f9c-89b3-e0317962472b.aspx).
+
+    **Note**: A browser that uses ClickOnce to download (like Internet Explorer or Edge) is needed to complete the next step.
 
   2. In the EAC, go to **Hybrid** > **Setup** and click the appropriate **Configure** button to download the Exchange Online Remote PowerShell Module for multi-factor authentication.
 

exchange/docs-conceptual/exchange-online/disable-access-to-exchange-online-powershell.md

@@ -3,12 +3,13 @@ title: "Enable or disable access to Exchange Online PowerShell"
 ms.author: chrisda
 author: chrisda
 manager: serdars
-ms.date: 2/20/2018
+ms.date: 
 ms.audience: Admin
 ms.topic: article
 ms.service: exchange-online
 localization_priority: Normal
 ms.assetid: f969816a-2607-4655-9d47-9e8767fb5633
+search.appverid: MET150
 description: "Admins can learn how to enable or disable access to Exchange Online PowerShell for users in their organization"
 ---
 
 ```
 
 ```
-$ | foreach {Set-User -RemotePowerShellEnabled $false}
+$ | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false}
 ```
 
 This example removes access to Exchange Online PowerShell for all users whose **Title** attribute contains the value "Sales Associate".
@@ -68,7 +69,7 @@ $DSA = Get-User -ResultSize unlimited -Filter {(RecipientType -eq 'UserMailbox')
 ```
 
 ```
-$DSA | foreach {Set-User -RemotePowerShellEnabled $false}
+$DSA | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false}
 ```
 
 ### Use a list of specific users
@@ -80,10 +81,10 @@ $ = Get-Content 
 ```
 
 ```
-$ | foreach {Set-User -RemotePowerShellEnabled $false}
+$ | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false}
 ```
 
-This example uses the text file C:\My Documents\NoPowerShell.txt to identify the users by their email addresses. The text file must contain one email address on each line as follows:
+This example uses the text file C:\My Documents\NoPowerShell.txt to identify the users by their accounts. The text file must contain one account on each line as follows:
 
 ```
 [email protected]
@@ -98,7 +99,7 @@ $NPS = Get-Content "C:\My Documents\NoPowerShell.txt"
 ```
 
 ```
-$NPS | foreach {Set-User -RemotePowerShellEnabled $false}
+$NPS | foreach {Set-User -Identity $_.MicrosoftOnlineServicesID -RemotePowerShellEnabled $false}
 ```
 
 ## View the Exchange Online PowerShell access for users

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

@@ -9,6 +9,7 @@ ms.topic: article
 ms.service: exchange-online
 localization_priority: Normal
 ms.assetid: 1cb603b0-2961-4afe-b879-b048fe0f64a2
+search.appverid: MET150
 description: "Learn about using PowerShell in Exchange Online"
 ---