You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
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.
6
6
7
-
7
+
8
8
9
9
## Learn How To Contribute
10
10
@@ -19,19 +19,19 @@ Contributors who only make infrequent or small updates can edit the file directl
19
19
20
20
This brief video also covers how to contribute:
21
21
22
-
[](https://support.office.com/article/edit-powershell-cmdlet-in-github-dcd20227-3764-48ce-ad6e-763af8b48daf)
22
+
[](https://support.office.com/article/edit-powershell-cmdlet-in-github-dcd20227-3764-48ce-ad6e-763af8b48daf)
23
23
24
24
### Quickly update an article using GitHub.com
25
25
26
26
1. Make sure you're signed in to GitHub.com with your GitHub account.
27
27
2. Go to the page you want to edit on docs.microsoft.com.
28
28
3. On the right-hand side of the page, click **Edit** (pencil icon).
29
29
30
-
30
+
31
31
32
32
4. The corresponding topic file on GitHub opens, where you need to click the **Edit this file** pencil icon.
33
33
34
-
34
+
35
35
36
36
5. The topic opens in a line-numbered editing page where you can make changes to the file.
37
37
@@ -45,7 +45,7 @@ This brief video also covers how to contribute:
45
45
46
46
- 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).
47
47
48
-
48
+
49
49
50
50
6. You can click the **Preview changes** tab to see what the changes will look like.
51
51
@@ -56,15 +56,15 @@ This brief video also covers how to contribute:
56
56
57
57
When you're ready, click the green **Propose file change** button.
9. On the **Open a pull request** page that appears, click the green **Create pull request** button.
66
66
67
-
67
+
68
68
69
69
> [!NOTE]
70
70
> Your permissions in the repo determine what you see in the last several steps. People with no special privileges will see the **Propose file change** section and subsequent confirmation pages as described. People with permissions to create and approve their own pull requests will see a similar **Commit changes** section with extra options for creating a new branch and fewer confirmation pages.<br/><br/>The point is: click any green buttons that are presented to you until there are no more.
4. On the **App registrations** page that opens, click **New registration**.
120
120
121
-
121
+
122
122
123
123
On the **Register an application** page that opens, configure the following settings:
124
124
@@ -130,7 +130,7 @@ For a detailed visual flow about creating applications in Azure AD, see <https:/
130
130
131
131
Note that you can't create credentials for [native applications](/azure/active-directory/manage-apps/application-proxy-configure-native-client-application), because you can't use that type for automated applications.
132
132
133
-
133
+
134
134
135
135
When you're finished, click **Register**.
136
136
@@ -143,7 +143,7 @@ For a detailed visual flow about creating applications in Azure AD, see <https:/
143
143
144
144
1. On the app page under **Management**, select **Manifest**.
145
145
146
-
146
+
147
147
148
148
2. On the **Manifest** page that opens, find the `requiredResourceAccess` entry (on or about line 44).
149
149
@@ -167,21 +167,21 @@ For a detailed visual flow about creating applications in Azure AD, see <https:/
167
167
168
168
3. Still on the **Manifest** page, under **Management**, select **API permissions**.
169
169
170
-
170
+
171
171
172
172
On the **API permissions** page that opens, do the following steps:
173
173
174
174
-**API / Permissions name**: Verify the value **Exchange.ManageAsApp** is shown.
175
175
176
176
-**Status**: The current incorrect value is **Not granted for \<Organization\>**, and this value needs to be changed.
177
177
178
-
178
+
179
179
180
180
Select **Grant admin consent for \<Organization\>**, read the confirmation dialog that opens, and then click **Yes**.
181
181
182
182
The **Status** value should now be **Granted for \<Organization\>**.
4. Close the current **API permissions** page (not the browser tab) to return to the **App registrations** page. You'll use it in an upcoming step.
187
187
@@ -220,25 +220,25 @@ After you register the certificate with your application, you can use the privat
220
220
2. Under **Manage Azure Active Directory**, click **View**.
221
221
3. Under **Manage**, select **App registrations**.
222
222
223
-
223
+
224
224
225
225
2. On the application page that opens, under **Manage**, select **Certificates & secrets**.
226
226
227
-
227
+
228
228
229
229
3. On the **Certificates & secrets** page that opens, click **Upload certificate**.
230
230
231
-
231
+
232
232
233
233
In the dialog that opens, browse to the self-signed certificate (`.cer` file) that you created in [Step 3](#step-3-generate-a-self-signed-certificate).
234
234
235
-
235
+
236
236
237
237
When you're finished, click **Add**.
238
238
239
239
The certificate is now shown in the **Certificates** section.
240
240
241
-
241
+
242
242
243
243
4. Close the current **Certificates & secrets** page, and then the **App registrations** page to return to the main <https://portal.azure.com/> page. You'll use it in the next step.
244
244
@@ -258,26 +258,26 @@ For general instructions about assigning roles in Azure AD, see [View and assign
258
258
259
259
1. On the Azure AD portal at <https://portal.azure.com/>, under **Manage Azure Active Directory**, click **View**.
260
260
261
-
261
+
262
262
263
263
2. On the **Overview** page that opens, under **Manage**, select **Roles and administrators**.
264
264
265
-
265
+
266
266
267
267
3. On the **Roles and administrators** page that opens, find and select one of the supported roles by _clicking on the name of the role_ (not the check box) in the results.
268
268
269
-
269
+
270
270
271
271
4. On the **Assignments** page that opens, click **Add assignments**.
272
272
273
-
273
+
274
274
275
275
5. In the **Add assignments** flyout that opens, find and select the app that you created in [Step 1](#step-1-register-the-application-in-azure-ad).
276
276
277
-
277
+
278
278
279
279
When you're finished, click **Add**.
280
280
281
281
6. Back on the **Assignments** page, verify that the app has been assigned to the role.
282
282
283
-
283
+
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/connect-to-exchange-online-powershell.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -104,13 +104,13 @@ For other sign in methods that are available in PowerShell 7, see the [PowerShel
104
104
105
105
3. In the sign-in window that opens, enter your password, and then click **Sign in**.
106
106
107
-
107
+
108
108
109
109
4.**MFA only**: A verification code is generated and delivered based on the response option that's configured for your account (for example, a text message or the Microsoft Authenticator app on your device).
110
110
111
111
In the verification window that opens, enter the verification code, and then click **Verify**.
112
112
113
-
113
+
114
114
115
115
For detailed syntax and parameter information, see [Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline).
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/v1-module-mfa-connect-to-exo-powershell.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -75,11 +75,11 @@ You need to do the following steps in a browser that supports ClickOnce (for exa
75
75
76
76
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.
77
77
78
-
78
+
79
79
80
80
3. In the **Application Install** window that opens, click **Install**.
81
81
82
-
82
+
83
83
84
84
- When you use the Exchange Online Remote PowerShell Module, your session will end after one hour, which can be problematic for long-running scripts or processes. To avoid this issue, use [Trusted IPs](/azure/active-directory/authentication/howto-mfa-mfasettings#trusted-ips) to bypass MFA for connections from your intranet. Trusted IPs allow you to connect to Exchange Online PowerShell from your intranet using the old instructions at [Basic auth - Connect to Exchange Online PowerShell](basic-auth-connect-to-exo-powershell.md). Also, if you have servers in a datacenter, be sure to add their public IP addresses to Trusted IPs as described [here](/azure/active-directory/authentication/howto-mfa-mfasettings#enable-the-trusted-ips-feature-by-using-service-settings).
85
85
@@ -132,13 +132,13 @@ You need to do the following steps in a browser that supports ClickOnce (for exa
132
132
133
133
3. In the sign-in window that opens, enter your password, and then click **Sign in**.
134
134
135
-
135
+
136
136
137
137
A verification code is generated and delivered based on the verification response option that's configured for your account (for example, a text message or the Azure Authenticator app on your mobile phone).
138
138
139
139
4. In the verification window that opens, enter the verification code, and then click **Sign in**.
140
140
141
-
141
+
142
142
143
143
> [!NOTE]
144
144
> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Exchange Online Remote PowerShell Module 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 all currently open PowerShell sessions in the current window, run the following command:
0 commit comments