Merge pull request #6 from MicrosoftDocs/master

Merge latest to own fork

Author: islubin

.openpublishing.publish.config.json

@@ -88,9 +88,9 @@
       ]
     },
     {
-      "docset_name": "teams-ps",
-      "build_source_folder": "teams",
-      "build_output_subfolder": "teams-ps",
+      "docset_name": "staffhub-ps",
+      "build_source_folder": "staffhub",
+      "build_output_subfolder": "staffhub-ps",
       "locale": "en-us",
       "monikers": [],
       "moniker_ranges": [],
@@ -117,9 +117,38 @@
       ]
     },
     {
-      "docset_name": "staffhub-ps",
-      "build_source_folder": "staffhub",
-      "build_output_subfolder": "staffhub-ps",
+      "docset_name": "exchange-ps",
+      "build_source_folder": "exchange",
+      "build_output_subfolder": "exchange-ps",
+      "locale": "en-us",
+      "monikers": [],
+      "moniker_ranges": [],
+      "open_to_public_contributors": true,
+      "type_mapping": {
+        "Conceptual": "Content",
+        "ManagedReference": "Content",
+        "RestApi": "Content",
+        "AzurePsModulePage": "Content"
+      },
+      "build_entry_point": "docs",
+      "template_folder": "_themes",
+      "version": 0,
+      "customized_template_paths": [
+        "_dependentPackages/azurecli.plugins/azurecli"
+      ],
+      "customized_tasks": {
+        "docset_prebuild": [
+          "_dependentPackages/CommonPlugins/tools/PowerShellReference.ps1"
+        ]
+      },
+      "monikerPath": [
+        "mapping/monikerMapping.json"
+      ]
+    },
+    {
+      "docset_name": "teams-ps",
+      "build_source_folder": "teams",
+      "build_output_subfolder": "teams-ps",
       "locale": "en-us",
       "monikers": [],
       "moniker_ranges": [],
@@ -173,11 +202,11 @@
     ]
   },
   "need_generate_pdf_url_template": true,
-  "Targets": {  
-    "Pdf": {  
-    "template_folder": "_themes.pdf"  
-    }  
-   },
+  "targets": {
+    "Pdf": {
+      "template_folder": "_themes.pdf"
+    }
+  },
   "need_generate_pdf": false,
   "need_generate_intellisense": false,
   "dependent_packages": [

README.md

@@ -25,7 +25,7 @@ When you contribute your work will go directly into the Microsoft Office product
 **Note** that 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 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. 
+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.
    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 

exchange/docfx.json

@@ -39,6 +39,7 @@
           "**/*.png",
           "**/*.jpg"
         ],
+        "version": "exchange-ps",
         "exclude": [
           "**/obj/**",
           "**/includes/**"
@@ -59,10 +60,13 @@
       "ms.date" : "09/25/2017",
       "ms.topic" : "reference",
       "ms.service" : "exchange-powershell",
-      "ms.devlang" : "powershell"
+      "ms.devlang" : "powershell",
+      "feedback_system": "GitHub",
+      "feedback_github_repo": "MicrosoftDocs/office-docs-powershell",
+      "feedback_product_url": "https://github.com/MicrosoftDocs/office-docs-powershell/issues"
     },
     "fileMetadata": {},
     "template": [],
     "dest": "exchange-ps"
   }
-}
+}

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

@@ -0,0 +1,113 @@
+---
+title: "Connect to Exchange Online Protection PowerShell"
+ms.author: chrisda
+author: chrisda
+manager: serdars
+ms.date: 7/10/2017
+ms.audience: Admin
+ms.topic: article
+ms.service: eop
+localization_priority: Normal
+ms.assetid: 054e0fd7-d465-4572-93f8-a00a9136e4d1
+description: "Use remote PowerShell to connect to an Exchange Online Protection organization"
+---
+
+# Connect to Exchange Online Protection PowerShell
+
+Exchange Online Protection PowerShell allows you to manage your Exchange Online Protection settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Exchange Online Protection. It's a simple three-step process where you enter your Office 365 credentials, provide the required connection settings, and then import the Exchange Online Protection cmdlets into your local Windows PowerShell session so that you can use them.
+  
+## What do you need to know before you begin?
+
+- Estimated time to complete: 5 minutes
+    
+- You can use the following versions of Windows:
+    
+  - Windows 10
+    
+  - Windows 8.1
+    
+  - Windows Server 2016
+    
+  - Windows Server 2012 or Windows Server 2012 R2
+    
+  - Windows 7 Service Pack 1 (SP1)\*
+    
+  - Windows Server 2008 R2 SP1\*
+    
+  \* You need to install the Microsoft.NET Framework 4.5 or later and then either the Windows Management Framework 3.0 or the Windows Management Framework 4.0. For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868) and [Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757) or [Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344).
+    
+- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You get the following error when you try to connect:
+    
+     `Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.`
+    
+    To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
+    
+  ```
+  Set-ExecutionPolicy RemoteSigned
+  ```
+
+    You need to configure this setting only once on your computer, not every time you connect.
+    
+> [!TIP]
+> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612), [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). 
+  
+## Connect to Exchange Online Protection
+
+1. On your local computer, open Windows PowerShell and run the following command.
+    
+   ```
+   $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.
+    
+    ```
+    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
+    ```
+
+     **Notes**:
+    
+   - For Office 365 Germany, use the  _ConnectionUri_ value: `https://ps.protection.outlook.de/powershell-liveid/`
+    
+   - For Exchange Online Protection subscriptions that are Exchange Enterprise CAL with Services (includes data loss prevention (DLP) and reporting using web services), use the  _ConnectionUri_ value: `https://outlook.office365.com/powershell-liveid/`
+    
+3. Run the following command.
+    
+   ```
+   Import-PSSession $Session
+   ```
+
+      [!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: 
+  
+   ```
+   Remove-PSSession $Session
+   ```
+
+## How do you know this worked?
+
+After Step 3, the Exchange Online Protection cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange Online Protection cmdlet, for example, **Get-TransportRule**, and see the results.
+  
+If you receive errors, check the following requirements:
+  
+- A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1.
+    
+- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online Protection organization.
+    
+- 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
+
+The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics.
+  
+- [Get-Credential](https://go.microsoft.com/fwlink/p/?LinkId=389618)
+    
+- [New-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389621)
+    
+- [Import-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389619)
+    
+- [Remove-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389620)
+    
+- [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623)

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

@@ -0,0 +1,29 @@
+---
+title: "Exchange Online Protection PowerShell"
+ms.author: chrisda
+author: chrisda
+manager: serdars
+ms.date: 2/20/2018
+ms.audience: Admin
+ms.topic: article
+ms.service: eop
+localization_priority: Normal
+ms.assetid: f7918a88-774a-405e-945b-bc2f5ee9f748
+description: "Learn about using PowerShell in Exchange Online Protection"
+---
+
+# Exchange Online Protection PowerShell
+
+Exchange Online Protection PowerShell is the administrative interface that enables you to manage your Exchange Online Protection (EOP) organization from the command line. For example, you can use Exchange Online Protection PowerShell to configure mail flow rules (also known as transport rules) and connectors. The following topics provide information about using Exchange Online Protection PowerShell:
+  
+- To create a remote PowerShell session to your Exchange Online Protection organization, see [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md).
+  
+- For a sample script that lets admins who manage multiple tenants (companies) apply configuration settings to their tenants, see [Sample script for applying EOP settings to multiple tenants](http://technet.microsoft.com/library/e87e84e1-7be0-44bf-a414-d91d60ed8817.aspx).
+  
+- The following introductory video shows you how to connect to and use Exchange Online Protection PowerShell.
+  
+  **Note:** This video applies to Exchange Online and EOP organizations. When you connect to your organization, be careful to specify the correct URL (_ConnectionUri_ value). The required URL is different for Exchange Online and EOP organizations.
+  
+  [Use Remote PowerShell in EOP](https://videoplayercdn.osi.office.net/hub/?csid=ux-cms-en-us-msoffice&uuid=9cb28006-c2cb-45b6-b72e-eeed8767dee7&AutoPlayVideo=false)
+  
+

exchange/docs-conceptual/exchange-eop/media/MSN_Video_Widget.gif

@@ -0,0 +1,120 @@
+---
+title: "Connect to Exchange Online PowerShell"
+ms.author: chrisda
+author: chrisda
+manager: serdars
+ms.date: 7/10/2017
+ms.audience: Admin
+ms.topic: article
+ms.service: exchange-online
+localization_priority: Normal
+ms.custom: Strat_EX_Admin
+ms.assetid: c8bea338-6c1a-4bdf-8de0-7895d427ee5b
+description: "Learn how to use remote PowerShell to connect to Exchange Online."
+---
+
+# Connect to Exchange Online PowerShell
+Exchange Online PowerShell allows you to manage your Exchange Online settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Exchange Online. It's a simple three-step process where you enter your Office 365 credentials, provide the required connection settings, and then import the Exchange Online cmdlets into your local Windows PowerShell session so that you can use them.
+  
+> [!IMPORTANT]
+> If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you need to download and use the Exchange Online Remote PowerShell Module. For more information, see [Connect to Exchange Online PowerShell using multi-factor authentication](mfa-connect-to-exchange-online-powershell.md). If you're an Exchange Online Protection (EOP) standalone customer, and you're using the service to protect on-premises mailboxes, use the connection instructions in the topic [Connect to Exchange Online Protection PowerShell](../../exchange-eop/connect-to-exchange-online-protection-powershell.md). If your EOP subscription is Exchange Enterprise CAL with Services (includes data loss prevention (DLP) and reporting using web services), the connection instructions in this topic will work for you. 
+  
+## What do you need to know before you begin?
+
+- Estimated time to complete: 5 minutes
+    
+- You can use the following versions of Windows:
+    
+  - Windows 10
+    
+  - Windows 8.1
+    
+  - Windows Server 2016
+    
+  - Windows Server 2012 or Windows Server 2012 R2
+    
+  - Windows 7 Service Pack 1 (SP1)\*
+    
+  - Windows Server 2008 R2 SP1\*
+    
+    \* You need to install the Microsoft.NET Framework 4.5 or later and then either the Windows Management Framework 3.0 or the Windows Management Framework 4.0. For more information, see [Installing the .NET Framework](https://go.microsoft.com/fwlink/p/?LinkId=257868) and[Windows Management Framework 3.0](https://go.microsoft.com/fwlink/p/?LinkId=272757) or[Windows Management Framework 4.0](https://go.microsoft.com/fwlink/p/?LinkId=391344).
+    
+- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You get the following error when you try to connect:
+    
+     `Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.`
+    
+    To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting **Run as administrator**):
+    
+  ```
+  Set-ExecutionPolicy RemoteSigned
+  ```
+
+    You need to configure this setting only once on your computer, not every time you connect.
+    
+    
+> [!TIP]
+> Having problems? Ask for help in the Exchange forums. Visit the forums at: [Exchange Online](https://go.microsoft.com/fwlink/p/?linkId=267542), or [Exchange Online Protection](https://go.microsoft.com/fwlink/p/?linkId=285351). 
+  
+## Connect to Exchange Online PowerShell
+
+1. On your local computer, open Windows PowerShell and run the following command.
+    
+    ```
+    $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.
+    
+   ```
+   $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication  Basic -AllowRedirection
+   ```
+
+    **Notes**:
+    
+    - 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/`
+    
+3. Run the following command.
+    
+    ```
+    Import-PSSession $Session
+    ```
+
+> [!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. 
+  
+  ```
+  Remove-PSSession $Session
+  ```
+
+## How do you know this worked?
+
+After Step 3, the Exchange Online cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange Online cmdlet, for example, **Get-Mailbox**, and see the results.
+  
+If you receive errors, check the following requirements:
+  
+- A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1.
+    
+- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online organization.
+    
+- 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.
+    
+## See also
+
+The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics.
+  
+- [Get-Credential](https://go.microsoft.com/fwlink/p/?LinkId=389618)
+    
+- [New-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389621)
+    
+- [Import-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389619)
+    
+- [Remove-PSSession](https://go.microsoft.com/fwlink/p/?LinkId=389620)
+    
+- [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623)
+    
+