Forum Discussion
18th Aug Update - Secure release is now broken for common Intune MAM and BYOD scenarios
I know it's not ideal, but can't you exclude Universal Print from your conditional access policy? That would probably fix the problem.
- BradHSep 15, 2026Brass Contributor
The scenario is as follows:
We have a bunch of users who have Copilot app installed. It's browser agnostic, it's signed in, and its supported by MAM/BYOD. They go to print and it just works because you don't have to be on Edge and in a work profile. Copilot takes that weight.
In the new scenario, staff try and release print jobs but it's going to try and do it via their default browser. Now, in this world and while Microsoft would absolutely love staff on MAM to use Edge as their default browser, there are a lot of that use Chrome, and or Safari (depending on your poison of mobile flavour) and it's going to bork if it is not in a "staff" profile.
We have MAM for a reason. We shouldn't need to disable components to make something as simple as printing to work.