Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 17 additions & 3 deletions exchange/docs-conceptual/exchange-online-powershell-v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V3 module
ms.author: chrisda
author: chrisda
manager: deniseb
ms.date: 10/28/2024
ms.date: 02/25/2025
ms.audience: Admin
audience: Admin
ms.topic: article
Expand Down Expand Up @@ -613,14 +613,28 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo

### Current release

#### Version 3.7.1

- Added a new property named `ExoExchangeSecurityDescriptor` to the output of **Get-EXOMailbox** that's similar to the `ExchangeSecurityDescriptor` property in the output of **Get-Mailbox**.
- Added new cmdlets to support the Viva Org Insights Delegation feature:
- **Add-VivaOrgInsightsDelegatedRole**
- **Get-VivaOrgInsightsDelegatedRole**
- **Remove-VivaOrgInsightsDelegatedRole**

### Previous releases

#### Version 3.7.0

- Integrated Web Account Manager (WAM) in authentication flows to enhance security.
- Command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ parameter in the **Connect-ExchangeOnline** command so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet.
- Fixed connection issues with app only authentication in Security & Compliance PowerShell.

#### Version 3.6.0

- **Get-VivaModuleFeature** now returns information about the kinds of identities that the feature supports creating policies for (for example, users, groups, or the entire tenant).
- Cmdlets for Viva feature access management now handle continuous access evaluation (CAE) claim challenges.
- Added fix for compatibility issue with the Microsoft.Graph module.

### Previous releases

#### Version 3.5.1

- Bug fixes in **Get-EXOMailboxPermission** and **Get-EXOMailbox**.
Expand Down
14 changes: 14 additions & 0 deletions exchange/docs-conceptual/whats-new-in-the-exo-module.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,20 @@ description: "Learn about the new features and functionality available in the la

This article lists new features in the Exchange Online PowerShell module that's used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. Features that are currently in preview are denoted with **(preview)**.

## January 2025

- [Version 3.7.1](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.1)

For information about what's in this release, see [Version 3.7.1](exchange-online-powershell-v2.md#version-371).

## December 2024

- [Version 3.7.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.0)

Starting with this version of the module, command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ parameter in the **Connect-ExchangeOnline** command so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet.

For information about what's in this release, see [Version 3.7.0](exchange-online-powershell-v2.md#version-370).

## September 2024

- [Version 3.6.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.6.0)
Expand Down
3 changes: 1 addition & 2 deletions exchange/exchange-ps/exchange/Set-ServerComponentState.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,7 @@ The first command changes the state of all server components to Inactive.

The second command changes the state to Active after the maintenance is over (required).

> [!NOTE]
> By design, the Microsoft Exchange IMAP4 and Microsoft Exchange POP3 services stop if the related `ImapProxy` and `PopProxy` components are in the Inactive state. The services may need to be manually started after the related `ImapProxy` and `PopProxy` components are changed to the Active state.
**Note**: By design, the Microsoft Exchange IMAP4 and Microsoft Exchange POP3 services stop if the related `ImapProxy` and `PopProxy` components are in the Inactive state. You might need to manually restart the services after the related `ImapProxy` and `PopProxy` components are changed to the Active state.

## PARAMETERS

Expand Down