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
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
---
2
-
ms.date: 05/16/2025
2
+
ms.date: 09/18/2025
3
3
---
4
4
5
5
# Overview
6
6
7
7
## Learn how to contribute
8
8
9
-
Anyone who is interested can contribute to the articles. When you contribute, your work goes into the content set after it's been reviewed and merged. It's then published to [Microsoft Learn](https://learn.microsoft.com/), and you're listed as a contributor at: <https://github.com/MicrosoftDocs/office-docs-powershell/graphs/contributors>.
9
+
Anyone interested can contribute to articles. When you contribute, your work goes into the content set after someone reviews and merges it. Your updates are published to [Microsoft Learn](https://learn.microsoft.com/), and you're listed as a contributor at: <https://github.com/MicrosoftDocs/office-docs-powershell/graphs/contributors>.
10
10
11
-
If you get stuck and are a Microsoft employee or vendor, post a message to [Ask an Admin](https://aka.ms/askanadmin).
11
+
Microsoft employees or vendors who get stuck can post a question to [Ask an Admin](https://aka.ms/askanadmin).
12
12
13
13
### Quickly update an article using GitHub.com
14
14
@@ -17,34 +17,34 @@ Contributors who make infrequent or small updates can edit the file directly on
17
17
> [!TIP]
18
18
> To edit an article, you need to get to it on the GitHub.com backend. If you're already on the GitHub.com page of the article, you're starting at step 4.
19
19
>
20
-
> Your permissions in the repo determine what you see in step 5 and later. People with no special privileges see the steps as described. People with permissions to approve their own pull requests see a similar experience with different button and page titles (for example, **Commit changes** instead of **Propose changes**), extra options for creating a new branch, and fewer confirmation pages. The point is: click any green buttons that are presented to you until there are no more.
20
+
> Your permissions in the repo determine what you see in step 5 and later. People with no special privileges see the steps as described. People with permissions to approve their own pull requests see a similar experience with different button and page titles (for example, **Commit changes** instead of **Propose changes**), extra options for creating a new branch, and fewer confirmation pages. The point is: Select any green buttons presented to you until there are no more.
21
21
22
-
1. Verify that you're signed in to GitHub.com with your GitHub account.
23
-
2. On learn.microsoft.com, find the article that you want to update.
24
-
3. Above the title of the article, select **Edit this document**.
22
+
1. Verify you're signed in to GitHub.com with your GitHub account.
23
+
2. On learn.microsoft.com, find the article you want to update.
24
+
3. Above the article title, select **⋮****More actions \>**Edit**.
25
25
26
-
26
+
27
27
28
-
4. The corresponding article file opens on GitHub. Select **Edit**.
28
+
4. The corresponding article file opens on GitHub. Select **Edit this file**.
29
29
30
-
30
+
31
31
32
32
5. If a **You need to fork this repository to propose changes** page opens, select **Fork this repository**.
33
33
34
-
34
+
35
35
36
36
6. The article file opens in a line-numbered editor page where you can make updates.
37
37
38
38
Articles on learn.microsoft.com are formatted using the Markdown language. For help on using Markdown, see [Mastering Markdown](https://guides.github.com/features/mastering-markdown/).
39
39
40
40
> [!TIP]
41
-
> Cmdlet reference articles follow a very strict schema with limited formatting options, because the articles are also converted and used for help at the command line (`Get-Help <CmdletName>`). Use existing content as a guide. For more information, see [platyPS Schema](https://github.com/PowerShell/platyPS/blob/master/docs/developer/platyPS/platyPS.schema.md).
41
+
> Cmdlet reference articles follow a strict schema with limited formatting options, because the articles are also converted and used for help at the command line (`Get-Help <CmdletName>`). Use existing content as a guide. For more information, see [platyPS Schema](https://github.com/PowerShell/platyPS/blob/master/docs/developer/platyPS/platyPS.schema.md).
42
42
43
43
Select **Preview** to view your changes as you go. Select **Edit** to go back to making updates.
44
44
45
45
When you're finished making changes, select the green **Commit changes** button.
46
46
47
-
47
+
48
48
49
49
7. In the **Propose changes** dialog that opens, review and/or enter the following values:
50
50
-**Commit message**: This value is required. You can accept the default value ("Update \<filename\>") or you can change it.
@@ -54,37 +54,37 @@ Contributors who make infrequent or small updates can edit the file directly on
54
54
55
55
When you're finished on the **Propose changes** dialog, select the green **Propose changes** button.
56
56
57
-
57
+
58
58
59
59
8. On the **Comparing changes** page that opens, select the green **Create pull request** button.
60
60
61
-
61
+
62
62
63
63
9. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button.
64
64
65
-
65
+
66
66
67
67
10. That's it. There's nothing more for you to do.
68
68
69
-
The article owner (identified in metadata) is notified about the changes to the article. Eventually, the article owner or another party will review, possibly edit, and approve your changes. After your pull request is merged, the article is updated on learn.microsoft.com.
69
+
The article owner (identified in metadata) is notified about the changes to the article. Eventually, the article owner or another party reviews, possibly edits, and approves your changes. After the reviewer merges your pull request, the article is updated on learn.microsoft.com.
70
70
71
71
## Microsoft Open Source Code of Conduct
72
72
73
-
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
73
+
This project adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
74
74
75
75
For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any questions or comments.
76
76
77
77
### Contributing
78
78
79
-
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 the rights to use your contribution. For details, visit <https://cla.microsoft.com>.
79
+
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 the rights to use your contribution. For details, visit <https://cla.microsoft.com>.
80
80
81
81
When you submit a pull request, a CLA-bot automatically determines whether you need to provide a CLA and decorate the PR appropriately (for example, label, comment). Follow the instructions provided by the bot. You only need to do this step once across all repos using our CLA.
82
82
83
83
### Legal Notices
84
84
85
85
Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the [LICENSE-CODE](LICENSE-CODE) file.
86
86
87
-
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries/regions.
87
+
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation might be either trademarks or registered trademarks of Microsoft in the United States and/or other countries/regions.
88
88
89
89
The licenses for this project don't grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at <https://go.microsoft.com/fwlink/?LinkID=254653>.
The TestCases parameter specifies the name of the test case to analyze. The available test cases and their required parameters are described in the following list:
282
282
283
-
- **Encryption_EvaluationDetails**: Validates email encryption evaluation details. No other parameters are required.
284
-
- **Encryption_LicenseAvailability**: Checks email encryption configurations. No other parameters are required.
285
-
- **MipLabels_EnabledEntities_ScopedLabels**: Shows the labels and label settings that apply to a user. Requires the UserPrincipalName parameter.
283
+
- **Encryption_EvaluationDetails**: Validates email encryption evaluation details. No other parameters are required. Runs Test-IRMConfiguration cmdlet as part of its checks.
284
+
- **Encryption_LicenseAvailability**: Checks email encryption configurations. No other parameters are required. Runs Get-IRMConfiguration, Get-RMSTemplate, Get-TransportRule, and Get-JournalRule cmdlets as part of its checks.
285
+
- **MipLabels_EnabledEntities_ScopedLabels**: Shows the labels and label settings that apply to a user. Requires the UserPrincipalName parameter. Runs Get-Label and Get-LabelPolicy cmdlets as part of its checks.
286
286
- **MipLabels_LicenseAvailability**: Verifies whether the MIP Label feature is enabled. No other parameters required.
287
287
- **DlpAlerts_CheckAlertsCreated**: Validates the DLP rule configuration for alerts created in last 5 days. Requires the DateTimeUTC parameter. The RuleName parameter is optional.
288
288
- **DlpAlerts_FindAlertForActivity**: Identifies missing alerts for an activity. Requires the DateTimeUTC parameter. The IncidentId and RecordId parameters are optional.
**Note**: This cmdlet is currently in Preview and is subject to change.
17
-
18
16
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
19
17
20
18
Use the Export-ContentExplorerData cmdlet to export data classification file details in Microsoft Purview compliance.
This example creates a DLP policy for Microsoft 365 Copilot (Preview) in several steps:
140
+
This example creates a DLP policy for Microsoft 365 Copilot in several steps:
141
141
142
142
- The first command returns information about all sensitivity labels. Select the GUID value of the sensitivity label that you want to use. For example, `e222b65a-b3a8-46ec-ae12-00c2c91b71c0`.
143
143
@@ -320,10 +320,12 @@ The EnforcementPlanes parameter defines the layer where policy actions are run.
320
320
321
321
`-EnforcementPlanes @("<Value>")`.
322
322
323
-
Currently, supported values are:
323
+
Valid values are:
324
324
325
-
- Entra: For use with policies applied to Entra-registered enterprise applications in the organization.
326
325
- Browser: For use with policies applied to unmanaged cloud apps in Edge for Business.
326
+
- CopilotExperiences
327
+
- Entra: For use with policies applied to Entra-registered enterprise applications in the organization.
The Locations parameter specifies to whom, what, and where the DLP policy applies. This parameter uses the following properties:
549
551
550
552
- Workload: What the DLP policy applies to. Use the value `Applications`.
551
-
- Location: Where the DLP policy applies. For Microsoft 365 Copilot, (Preview), use the value `470f2276-e011-4e9d-a6ec-20768be3a4b0`.
553
+
- Location: Where the DLP policy applies. For Microsoft 365 Copilot, use the value `470f2276-e011-4e9d-a6ec-20768be3a4b0`.
552
554
- Inclusions: Who the DLP policy applies to. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:<EmailAddress>}`. For security groups or distribution groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group,Identity:<ObjectId>}`. For the entire tenant, use this value: `{Type:"Tenant",Identity:"All"}`.
553
555
- Exclusions: Exclude security groups, distribution groups, or users from the scope of this DLP policy. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:<EmailAddress>}`. For groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group, Identity:<ObjectId>}`.
0 commit comments