Merge branch 'main' into patch-1

Author: chrisda

.openpublishing.redirection.teams.json

@@ -3014,6 +3014,11 @@
             "source_path": "teams/virtual-folder/teams/index.md",
             "redirect_url": "/powershell/module/microsoftteams/",
             "redirect_document_id": true
+        },
+        {
+            "source_path": "teams/virtual-folder/MicrosoftTeams/Set-CsGroupPolicyAssignment.md",
+            "redirect_url": "/powershell/module/microsoftteams/",
+            "redirect_document_id": false
         }
     ]
 }

README.md

@@ -1,14 +1,14 @@
 ---
-ms.date: 05/16/2025
+ms.date: 09/18/2025
 ---
 
 # Overview
 
 ## Learn how to contribute
 
-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>.
+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>.
 
-If you get stuck and are a Microsoft employee or vendor, post a message to [Ask an Admin](https://aka.ms/askanadmin).
+Microsoft employees or vendors who get stuck can post a question to [Ask an Admin](https://aka.ms/askanadmin).
 
 ### Quickly update an article using GitHub.com
 
@@ -17,34 +17,34 @@ Contributors who make infrequent or small updates can edit the file directly on
 > [!TIP]
 > 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.
 >
-> 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.
+> 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.
 
-1. Verify that you're signed in to GitHub.com with your GitHub account.
-2. On learn.microsoft.com, find the article that you want to update.
-3. Above the title of the article, select ![Edit this document icon.](images/m365-cc-sc-edit-icon.png) **Edit this document**.
+1. Verify you're signed in to GitHub.com with your GitHub account.
+2. On learn.microsoft.com, find the article you want to update.
+3. Above the article title, select **⋮** **More actions \> ![Edit icon.](images/quick-update-icon-learn-edit.png) **Edit**.
 
-   ![Screenshot of how to select the Edit this document button on a learn.microsoft.com article.](images/quick-update-edit-button-on-learn-page.png)
+   ![Screenshot of how to select Edit on a learn.microsoft.com article.](images/quick-update-01-edit-button-on-learn-page.png)
 
-4. The corresponding article file opens on GitHub. Select ![Edit icon.](images/quick-update-github-edit-icon.png) **Edit**.
+4. The corresponding article file opens on GitHub. Select ![Edit this file icon.](images/quick-update-icon-github-edit.png) **Edit this file**.
 
-   ![Screenshot of how to select the Edit button on a GitHub article file.](images/quick-update-edit-button-on-github-page.png)
+   ![Screenshot of how to select Edit this file on a GitHub article file.](images/quick-update-02-edit-button-on-github-page.png)
 
 5. If a **You need to fork this repository to propose changes** page opens, select **Fork this repository**.
 
-   ![Screenshot of how to select Fork this repository on the You need to fork this repository to propose changes page.](images/quick-update-fork-this-repository-page.png)
+   ![Screenshot of how to select Fork this repository on the You need to fork this repository to propose changes page.](images/quick-update-03-fork-this-repository-page.png)
 
 6. The article file opens in a line-numbered editor page where you can make updates.
 
    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/).
 
    > [!TIP]
-   > 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).
+   > 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).
 
    Select **Preview** to view your changes as you go. Select **Edit** to go back to making updates.
 
    When you're finished making changes, select the green **Commit changes** button.
 
-   ![Screenshot of how to select the green Commit changes button on the article editor page.](images/quick-update-editor-page.png)
+   ![Screenshot of how to select the green Commit changes button on the article editor page.](images/quick-update-04-github-editor-page.png)
 
 7. In the **Propose changes** dialog that opens, review and/or enter the following values:
    - **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
 
    When you're finished on the **Propose changes** dialog, select the green **Propose changes** button.
 
-   ![Screenshot of how to select the green Propose changes button in the Propose changes dialog.](images/quick-update-propose-changes-dialog.png)
+   ![Screenshot of how to select the green Propose changes button in the Propose changes dialog.](images/quick-update-05-propose-changes-dialog.png)
 
 8. On the **Comparing changes** page that opens, select the green **Create pull request** button.
 
-   ![Screenshot of how to select the green Create pull request button on the Comparing changes page.](images/quick-update-comparing-changes-page.png)
+   ![Screenshot of how to select the green Create pull request button on the Comparing changes page.](images/quick-update-06-comparing-changes-page.png)
 
 9. On the **Open a pull request** page that opens, review the title and comments, and then select the green **Create pull request** button.
 
-   ![Screenshot of how to select the green Create pull request button on the Open a pull request page.](images/quick-update-open-a-pull-request-page.png)
+   ![Screenshot of how to select the green Create pull request button on the Open a pull request page.](images/quick-update-07-open-a-pull-request-page.png)
 
 10. That's it. There's nothing more for you to do.
 
-   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.
+   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.
 
 ## Microsoft Open Source Code of Conduct
 
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+This project adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
 
 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.
 
 ### 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 the rights to use your contribution. For details, visit <https://cla.microsoft.com>.
+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>.
 
 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.
 
 ### Legal Notices
 
 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.
 
-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.
+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.
 
 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>.
 

exchange/docs-conceptual/connect-exo-powershell-managed-identity.md

@@ -131,7 +131,7 @@ After you've successfully created the PowerShell runbook, do the following steps
 3. On the **Runbooks** flyout that opens, select the runbook.
 4. On the details page of the runbook, select **Start**.
 
-### Connect to Exchange Online PowerShell using Azure VMs with system-assigned managed identities
+### Connect to Exchange Online PowerShell using Azure VMs with user-assigned managed identities
 
 In a Windows PowerShell window in the Azure VM, use the command as described in the beginning of this section. For example:
 

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

@@ -228,13 +228,15 @@ The module is supported in the following versions of macOS:
 - **macOS 13 Ventura or later**:
 
   |Module version|PowerShell version|
-  |3.5.0 or later|7.4.0|
+  |---|---|
+  |3.5.0 or later|7.4.0 or later|
 
-  PowerShell 7.4.0 is the minimum supported version of PowerShell 7 in macOS 13 or later. Module versions 3.0.0 to 3.4.0 are also supported.
+  7.4.0 is the minimum supported version of PowerShell 7 in macOS 13 or later. Module versions 3.0.0 to 3.4.0 are also supported.
 
 - **macOS 12 Monterey** and **mac OS 11 Big Sur**:
 
   |Module version|PowerShell version|
+  |---|---|
   |3.5.0 or later|7.4.x|
   |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|
   |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|
@@ -243,7 +245,7 @@ The module is supported in the following versions of macOS:
 
   Module versions 2.0.4 and 2.0.5 run natively on Intel processors. Apple M1 or Apple M2 processors require Apple Rosetta 2.
 
-  macOS 11 and macOS 12 don't support PowerShell 7.5.x.
+  7.4.x is the latest supported version of PowerShell 7 in macOS 11 and macOS 12.
 
 - **macOS 10.15 Catalina**:
 
@@ -252,15 +254,15 @@ The module is supported in the following versions of macOS:
   |3.0.0 to 3.4.0|7.2.0 to 7.2.22|
   |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|
 
-  macOS 10.15 doesn't support PowerShell 7.3.x.
+  7.2.22 is the latest supported version of PowerShell 7 in macOS 10.15.
 
 - **macOS 10.14 Mojave**
 
   |Module version|PowerShell version|
   |---|---|
   |2.0.4 and 2.0.5|7.0.3 to 7.1.5|
 
-  macOS 10.14 doesn't support PowerShell 7.2.x.
+  7.1.5 is the latest supported version of PowerShell 7 in macOS 10.14.
 
 For instructions on installing PowerShell 7 on macOS, see [Installing PowerShell on macOS](/powershell/scripting/install/installing-powershell-core-on-macos).
 
@@ -294,7 +296,7 @@ The module is officially supported in the following distributions of Linux:
 
   |Module version|PowerShell version|
   |---|---|
-  |3.5.0 or later|7.4.x or later|
+  |3.5.0 or later|7.4.0 or later|
   |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|
 
 - **Ubuntu 20.04 LTS**
@@ -341,7 +343,7 @@ Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exc
   - Current versions of Windows include the required versions of the .NET Framework, so you don't need to install the .NET Framework to use the module in Windows PowerShell 5.1.
 
 - **PowerShell 7**:
-  - Module versions 3.5.0 (May 2024) or later require PowerShell 7.4.0 (November 2023) or later due to .NET 8.0 assembly dependencies. Earlier versions of PowerShell 7 might encounter compatibility issues (PowerShell 7.3.6 is more compatible than 7.3.7).
+  - Module versions 3.5.0 (May 2024) or later require PowerShell 7.4.0 (November 2023) or later due to .NET 8.0 assembly dependencies. Earlier versions of PowerShell 7 might encounter compatibility issues (PowerShell 7.3.6 is more compatible with the module than 7.3.7).
   - Module versions 3.0.0 (September 2022) to 3.4.0 (October 2023) require PowerShell 7.2.0 (November 2021) or later due to .NET 6.0 assembly dependencies in REST API cmdlets and connections.
   - Support for the module in PowerShell 7 started with version 2.0.4 (February 2021) in PowerShell 7.0.3 (July 2020).
 
@@ -355,7 +357,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |3.5.0 or later|7.4.0 or later|.NET 8.0<br/>Included in 24H2 or later.|
   |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
 
-  PowerShell 7.2.0 (.NET 6.0) is the earliest supported version in Windows 11.
+  7.2.0 (.NET 6.0) is the earliest supported version of PowerShell 7 in Windows 11.
 
 - **Windows Server 2022**:
 
@@ -365,7 +367,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |3.5.0 or later|7.4.0 or later|.NET 8.0|
   |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
 
-  PowerShell 7.2.0 (.NET 6.0) is the earliest supported version in Windows Server 2022.
+  7.2.0 (.NET 6.0) is the earliest supported version of PowerShell 7 in Windows Server 2022.
 
 - **Windows 10**:
 
@@ -393,7 +395,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |3.0.0 to 3.4.0|7.2.x|.NET 6.0|
   |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)|
 
-  PowerShell 7.2.22 (.NET 6.0) is the latest supported version in Windows 8.1, Windows Server 2012, and Windows Server 2012 R2.
+  7.2.22 (.NET 6.0) is the latest supported version of PowerShell 7 in Windows 8.1, Windows Server 2012, and Windows Server 2012 R2.
 
 - **Windows 7.1 SP1** and **Windows Server 2008 R2 SP1**:
 
@@ -402,7 +404,7 @@ Specific module version support in Windows depends on Windows PowerShell support
   |2.0.3|5.1|.NET Framework 4.7.1|
 
   > [!NOTE]
-  > Although you can install this version of the module, you can't connect to Exchange Online PowerShell, because version 7.0.3 lacks support for REST API connections.
+  > Although you can install this version of the module, you can't connect to Exchange Online PowerShell. Module version 2.0.3 lacks support for REST API connections.
 
 ### Prerequisites for the Exchange Online PowerShell module
 
@@ -699,18 +701,22 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 
 ### Current release
 
+#### Version 3.9.0
+
+- New _EnableSearchOnlySession_ switch on **Connect-IPPSSession**, which enables certain eDiscovery cmdlets and related cmdlets that connect to other Microsoft 365 services.
+
+### Previous releases
+
 #### Version 3.8.0
 
-- Support for providing an access token with **Connect-IPPSSession**.
+- New _AccessToken_ parameter on **Connect-IPPSSession**.
 - **Get-VivaModuleFeature** now returns information about ParentFeature, ChildFeature, and PolicyModes. These values represent parent and child features of a Viva app feature along with available enablement modes for future policies.  
 - New parameters _IsUserOptedInByDefault_ on the **Add-VivaModuleFeaturePolicy** and **Update-VivaModuleFeaturePolicy** cmdlets and the corresponding property value in all **\*-VivaModuleFeaturePolicy** cmdlets. The value indicates if users are opted in or out by the policy, as long as the user doesn't set a preference.
 
   You can use this parameter to keep the feature enabled in your organization while opting out the affected users by default, effectively soft disabling the feature for those users.
 
 - Deprecated the **Get-VivaFeatureCategory** cmdlet, all category-related parameters, and return values (_CategoryId_, _IsCategoryEnabled_).
 
-### Previous releases
-
 #### Version 3.7.2
 
 - The _DisableWAM_ switch is available on the **Connect-ExchangeOnline** cmdlet to disable Web Account Manager (WAM) if you get WAM-related connection errors.

exchange/docs-conceptual/whats-new-in-the-exo-module.md

@@ -22,11 +22,17 @@ description: "Learn about the new features and functionality available in the la
 
 This article lists new features in the Exchange Online PowerShell module used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and Exchange Online Protection PowerShell for cloud protection of on-premises email environments. Features that are currently in preview are denoted with **(preview)**.
 
+## August 2025
+
+- [Version 3.9.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.9.0)
+
+  For information about what's in this release, see [Version 3.9.0](exchange-online-powershell-v2.md#version-390).
+
 ## May 2025
 
 - [Version 3.8.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.8.0)
 
-  - For information about what's in this release, see [Version 3.8.0](exchange-online-powershell-v2.md#version-380).
+  For information about what's in this release, see [Version 3.8.0](exchange-online-powershell-v2.md#version-380).
 
 ## March 2025
 

exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md

@@ -59,7 +59,7 @@ This example finds all the mailboxes that are part of the Sales department and a
 
 After you verify the correct members are added to the role group, remove the WhatIf switch and run the command again.
 
-For more information about pipelining and the WhatIf parameter, see the following topics:
+For more information about pipelining and the WhatIf parameter, see the following articles:
 
 - [About Pipelines](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_pipelines)
 - [WhatIf, Confirm and ValidateOnly switches](https://learn.microsoft.com/exchange/whatif-confirm-and-validateonly-switches-exchange-2013-help)