Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Self Service Tools
Knowledge Base
My Account
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Support Essentials
Awards and Testimonials
License Agreement
Support Guide

Active Roles Product Notification

Return
Critical Alerts

Microsoft is deprecating support for Remote PowerShell (RPS) for Exchange Online Tenants as of June 1st, 2023 which impacts the ability of Active Roles to connect to Exchange Online.

 

How does this affect me?

Customers who have Active Roles configured to send emails (including email approvals) through Exchange Online will lose this functionality as of June 1st, 2023 unless they follow the steps under the Resolution section below. To determine if you have Office 365 Exchange Online configured as an email provider in the Active Roles mail configuration, please see KB 4341143

Resolution

This issue has already been addressed in 7.5.5, 7.6.3 and 8.0.1 by adding Support for the Exchange Online Management v3 module. It is recommended that all customers update to one of these versions before June 1st. There is no fix presently available for 8.1.1.

For customers on 8.1.1 or customers that are unable to update to 7.5.5, 7.6.3 and 8.0.1 before June 1st, Microsoft is allowing customers to extend the usage of Remote PowerShell (RPS) for Exchange Online Tenants until October 1st, 2023, however this must be completed by September, 2023. We recommend all customers using email via Exchange Online follow the steps outlined in Microsoft Blog 3779692 to extend RPS Support.

Status

One Identity is currently working to address this issue for 8.1.x and will provide a solution in an upcoming version by adding Support for the Exchange Online Management v3 module.

 

We apologize for the inconvenience this issue may have caused and we are working quickly correct it.