Skip to content

Update deployment-plan-protect-apps.md to be a bit more clear #4798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Yebbenbe
Copy link
Contributor

I've been working with InTune off and on for 3 months, and it still isn't clear what/when which policies apply, in what scenarios. From what I can tell, MAM (meaning, APP and ACP, but not Device Policies on managed apps) only applies to wrapped apps - not ANY app. This could be wrong - all of these docs blur together.

What I can't tell - whether Device Restrictions around Managed Apps ACTUALLY do anything to Apps added to the App Library.

I've been working with InTune off and on for 3 months, and it still isn't clear what/when which policies apply, in what scenarios. From what I can tell, MAM (meaning, APP and ACP, but not Device Policies on managed apps) only applies to wrapped apps - not ANY app. This could be wrong - all of these docs blur together. 

What I can't tell - whether Device Restrictions around Managed Apps ACTUALLY do anything to Apps added to the App Library.
Copy link
Contributor

@Yebbenbe : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 7aaa2a4:

✅ Validation status: passed

File Status Preview URL Details
intune/intune-service/fundamentals/deployment-plan-protect-apps.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants