In two previous blog posts, I wrote about enforcing limited web-only access on unmanaged devices using Conditional Access policies or Sensitivity Labels. However, in this blog post, I will talk about a third method that achieves a similar web experience for unmanaged devices by utilizing session policies in Microsoft Defender for Cloud Apps (MDCA).
You may wonder why you should choose this method over the others. Well, not only can we restrict downloading and printing of data, but we can also place other restrictions for example cut/copy data, which is not possible with the other methods. Additionally, user sessions with MDCA will go through a proxy, which will enable session monitoring, and allows for the possibility of generating alerts.
While Microsoft Defender for Cloud Apps offers many more possibilities, today we will focus on preventing data leakage from unmanaged devices by restricting downloads, cut, copy, and print actions in Microsoft 365.
This post is divided in the following sections;
To make use of the session policy features offered by Microsoft Defender for Cloud Apps, you will need to ensure that each user who benefits from these features has the following licenses assigned:
AND
Before proceeding to configure session policies in Microsoft Defender for Cloud Apps, we first need to create a Conditional Access policy. This policy will allow us to target specific user groups and enforce the session policies on those users.
Don’t worry, this policy will not take effect until we have created a session policy in Microsoft Defender for Cloud Apps.
If this is the first time you have created a Conditional Access app control policy, you will need to generate some activity in Microsoft Defender for Cloud Apps first. You can do this by signing into different M365 apps (such as OneDrive, Exchange Online, SharePoint Online, MS Teams) using at least one of the accounts included in the CA policy.
Afterwards, you can verify if the apps are connected to MDCA by visiting the Microsoft Defender admin center and going to Settings > Cloud Apps > Conditional Access App Control apps.
Please note that it may take a short while for the apps to be successfully connected.
With session policies in Microsoft Defender for Cloud Apps, we can enable real-time session monitoring and enforce specific restrictions on user activities. In this example, we will create two session policies to restrict cut, copy, print, and download actions on unmanaged devices.
Let’s start by creating a session policy to restrict cut, copy, and print actions first. Follow these steps:
Next, we can proceed to configure the second policy to restrict download actions. You can follow these steps:
After successfully creating the session policies in Microsoft Defender for Cloud Apps, our configuration is complete, and we can now examine the results.
Now, let’s sign in from an unmanaged device using a user account that is included in the Conditional Access policy we created earlier, and see what the user experience is like.
These restrictions will apply to the other Microsoft 365 services, including Microsoft Teams, OneDrive, Exchange Online, and SharePoint Online.
To wrap up this blog, I highly recommend considering blocking desktop app access for users working from unmanaged devices when implementing the session policies discussed here.
Without this, users will still be able to sign in to desktop apps and perform the actions like downloading, copying, cutting, and printing files from there. Do this at least until Microsoft offers similar capabilities to what Windows Information Protection (WIP) provided, which has been announced as discontinued.
However, recently, Microsoft announced Mobile Application Management (MAM) for Windows. Read this blog post, where I take a first look at this brand new feature.
This post is part of the unmanaged devices blog series; find more posts here. View previous part: Limited Access with Sensitivity Labels for Unmanaged Devices View next part: Block Access with Conditional Access for Unmanaged Devices |
Your email address will not be published. Required fields are marked *
8 Comments