Hi, I posted this in the Exchange Online group but they suggested I try here instead so: With the recent changes to the Azure Information Protection agent being discontinued we're experiencing a problem we never had before, at least we believe the two are connected. I'll explain our environment a little first: Azure enterprise agreement with all users having E5 licenses All users use Exchange online for most day to day business Sensitivity Labels deployed to all users A small number of users also have access to an on-premise Exchange server used for very specific business needs. This Exchange server is not federated with Exchange online and has a separate local Active Directory to hold the user accounts. Essentially it's an on-prem only setup as the data it holds is not allowed to be stored in the cloud Users of the on-prem Exchange have both their email accounts configured in the same Outlook profile Up until the recently users of the on-prem Exchange where able to pick from the labels published in Purview and use them when sending email from either their on-prem or online Exchange account but now when changing the from address field in Outlook to the on-prem one they lose access to the sensitivity button (becomes greyed out). Is this change expected? Is there something we can do to bring back the sensitivity button in Outlook when sending from the on-prem account? I've installed the new Purview Information Protection agent and tried making changes to UseOfficeForLabelling and AIPException but nothing gives us back the sensitivity button. Thanks

Purview Labels On Premise Exchange

James Misson 0

Hi,

I posted this in the Exchange Online group but they suggested I try here instead so:

With the recent changes to the Azure Information Protection agent being discontinued we're experiencing a problem we never had before, at least we believe the two are connected. I'll explain our environment a little first:

Azure enterprise agreement with all users having E5 licenses
All users use Exchange online for most day to day business
Sensitivity Labels deployed to all users
A small number of users also have access to an on-premise Exchange server used for very specific business needs. This Exchange server is not federated with Exchange online and has a separate local Active Directory to hold the user accounts. Essentially it's an on-prem only setup as the data it holds is not allowed to be stored in the cloud
Users of the on-prem Exchange have both their email accounts configured in the same Outlook profile

Up until the recently users of the on-prem Exchange where able to pick from the labels published in Purview and use them when sending email from either their on-prem or online Exchange account but now when changing the from address field in Outlook to the on-prem one they lose access to the sensitivity button (becomes greyed out).

Is this change expected? Is there something we can do to bring back the sensitivity button in Outlook when sending from the on-prem account? I've installed the new Purview Information Protection agent and tried making changes to UseOfficeForLabelling and AIPException but nothing gives us back the sensitivity button.

Thanks

Jake Zhang-MSFT 1,235 Reputation points Microsoft Vendor

2024-04-19T02:11:26.48+00:00

Hi @James Misson,

After reading your description, I think the issue is more related to Azure Information Protection. I have added the Azure Information Protection tag for you, and I hope your problem will be solved soon.
Givary-MSFT 28,061 Reputation points Microsoft Employee

2024-04-23T11:10:28.3933333+00:00

@James Misson Thank you for reaching out to us, to begin with

Request to check if E5 is correctly assigned to the affected user.

Ensure that all relevant Apps are properly checked in the licenses and apps configuration.

Does the affected user can see the Sensitivity button in OWA ?

Let me know if you have any further questions, feel free to post back.
James Misson 0 Reputation points

2024-04-24T08:37:23.0466667+00:00

Hi @Givary-MSFT

Yes all affected users have an E5 license assigned etc. The sensitivity button works when the user is sending from their 365 account and only becomes greyed out when changing the from field to use their on-prem Exchange account. I'm not able to test from OWA as we don't allow users to access it that way.

Thanks