Skip to content

Commit 1d8affb

Browse files
chrisdachrisda
committed
Merge branch 'master' into Ex2016CU12
2 parents c678a27 + 9a96bb5 commit 1d8affb

File tree

1,873 files changed

+41622
-35471
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,873 files changed

+41622
-35471
lines changed

‎.gitignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,3 +7,6 @@ _themes*/
77
.local/
88

99
.openpublishing.buildcore.ps1
10+
**/node_modules
11+
12+
\.idea/

‎README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Short URL: aka.ms/office-powershell
22

33
# Overview
4-
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.
4+
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 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.
55
![Contribution and Consumption model for Office PowerShell reference content](images/contrib-consumption-model.png)
66

77
# Learn How To Contribute

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ localization_priority: Priority
1111
ms.collection: Strat_EX_Admin
1212
ms.custom:
1313
ms.assetid: c8bea338-6c1a-4bdf-8de0-7895d427ee5b
14+
search.appverid: MET150
1415
description: "Learn how to use remote PowerShell to connect to Exchange Online."
1516
---
1617

@@ -123,4 +124,5 @@ The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more
123124
124125
- [Set-ExecutionPolicy](https://go.microsoft.com/fwlink/p/?LinkId=389623)
125126
127+
For more information about managing Office 365, see [Manage Office 365](https://docs.microsoft.com/en-us/Office365/).
126128

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,15 @@ ms.topic: article
88
ms.service: exchange-online
99
localization_priority: Normal
1010
ms.assetid: 04dae4ce-34a7-49c5-bf75-11e72452e04a
11+
search.appverid: MET150
1112
description: "Learn how to connect to Exchange Online PowerShell by using multi-factor authentication (MFA)."
1213
---
1314

1415
# Connect to Exchange Online PowerShell using multi-factor authentication
1516
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.
1617

1718
> [!NOTE]
18-
> 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.
19+
> • 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.
1920
2021
## What do you need to know before you begin?
2122

@@ -39,7 +40,9 @@ If you want to use multi-factor authentication (MFA) to connect to Exchange Onli
3940

4041
- The Exchange Online Remote PowerShell Module needs to be installed on your computer:
4142

42-
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).
43+
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).
44+
45+
**Note**: Internet Explorer or Edge is required because the download in the next step uses ClickOnce, so Google Chrome or Mozilla Firefox won't work.
4346

4447
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.
4548

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,13 @@ title: "Enable or disable access to Exchange Online PowerShell"
33
ms.author: chrisda
44
author: chrisda
55
manager: serdars
6-
ms.date: 2/20/2018
6+
ms.date:
77
ms.audience: Admin
88
ms.topic: article
99
ms.service: exchange-online
1010
localization_priority: Normal
1111
ms.assetid: f969816a-2607-4655-9d47-9e8767fb5633
12+
search.appverid: MET150
1213
description: "Admins can learn how to enable or disable access to Exchange Online PowerShell for users in their organization"
1314
---
1415

@@ -58,7 +59,7 @@ $<VariableName> = <Get-Mailbox | Get-User> -ResultSize unlimited -Filter <Filter
5859
```
5960

6061
```
61-
$<VariableName> | foreach {Set-User -RemotePowerShellEnabled $false}
62+
$<VariableName> | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false}
6263
```
6364

6465
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')
6869
```
6970

7071
```
71-
$DSA | foreach {Set-User -RemotePowerShellEnabled $false}
72+
$DSA | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false}
7273
```
7374

7475
### Use a list of specific users
@@ -80,10 +81,10 @@ $<VariableName> = Get-Content <text file>
8081
```
8182

8283
```
83-
$<VariableName> | foreach {Set-User -RemotePowerShellEnabled $false}
84+
$<VariableName> | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false}
8485
```
8586

86-
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:
87+
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:
8788

8889
```
8990
akol@contoso.com
@@ -98,7 +99,7 @@ $NPS = Get-Content "C:\My Documents\NoPowerShell.txt"
9899
```
99100

100101
```
101-
$NPS | foreach {Set-User -RemotePowerShellEnabled $false}
102+
$NPS | foreach {Set-User -Identity $_.MicrosoftOnlineServicesID -RemotePowerShellEnabled $false}
102103
```
103104

104105
## View the Exchange Online PowerShell access for users

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ ms.topic: article
99
ms.service: exchange-online
1010
localization_priority: Normal
1111
ms.assetid: 1cb603b0-2961-4afe-b879-b048fe0f64a2
12+
search.appverid: MET150
1213
description: "Learn about using PowerShell in Exchange Online"
1314
---
1415

‎exchange/docs-conceptual/exchange-server/exchange-management-shell.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,9 @@ A benefit of remote PowerShell is that you can use Windows PowerShell on a local
4343

4444
For details, see the following topics:
4545

46-
- [Exchange 2016 system requirements](https://technet.microsoft.com/library/aa996719(v=exchg.160).aspx)
46+
- [Exchange 2019 system requirements](https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019)
47+
48+
- [Exchange 2016 system requirements](https://docs.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016)
4749

4850
- [Exchange 2013 system requirements](https://technet.microsoft.com/library/aa996719(v=exchg.150).aspx)
4951

@@ -74,6 +76,6 @@ The following table provides links to topics that can help you learn about and u
7476
|[Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md)|Use Windows PowerShell on a local computer to connect to an Exchange server.|
7577
|[Control remote PowerShell access to Exchange servers](control-remote-powershell-access-to-exchange-servers.md)|Learn how to block or allow users' remote PowerShell access to Exchange servers.|
7678
|[Find the permissions required to run any Exchange cmdlet](find-exchange-cmdlet-permissions.md)|Find the permissions you need to run a specific cmdlet, or one or more parameters on the cmdlet.|
77-
|[Exchange cmdlet systax](exchange-cmdlet-syntax.md)|Learn about the structure and syntax of cmdlets in Exchange PowerShell.|
79+
|[Exchange cmdlet syntax](exchange-cmdlet-syntax.md)|Learn about the structure and syntax of cmdlets in Exchange PowerShell.|
7880
|[Recipient filters in Exchange Management Shell commands](recipient-filters/recipient-filters.md)|Learn about recipient filters in the Exchange Management Shell.|
79-
|[Use Update-ExchangeHelp to update Exchange PowerShell help topics on Exchange servers](use-update-exchangehelp.md)|Learn how to use Update-ExchangeHelp to update help for Exchange cmdlet reference topics on Exchange servers.|
81+
|[Use Update-ExchangeHelp to update Exchange PowerShell help topics on Exchange servers](use-update-exchangehelp.md)|Learn how to use Update-ExchangeHelp to update help for Exchange cmdlet reference topics on Exchange servers.|

‎exchange/docs-conceptual/exchange-server/open-the-exchange-management-shell.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,9 @@ When you open the Exchange Management Shell you can perform administrative tasks
3030
> [!TIP]
3131
> 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).
3232
33-
## Open the Exchange Management Shell in Windows 10
33+
## Open the Exchange Management Shell in Windows Server 2016 or Windows 10
3434

35-
Click **Start** > **All Apps** > **Microsoft Exchange Server 2016 \>** **Exchange Management Shell**.
35+
Click **Start** > **Microsoft Exchange Server 2016 \>** **Exchange Management Shell**.
3636

3737
## Open the Exchange Management Shell in Windows Server 2012 R2 or Windows 8.1
3838

0 commit comments

Comments
 (0)