Update apps-deploy.md

Added a note to confirm that we support nested groups in app assignments. This is needed due to some Azure AD documentation that is creating some confusing/conflicting information. https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-groups-membership-azure-portal#add-a-group-to-another-group
----------------------

 Important

We don't currently support:

Adding groups to a group synced with on-premises Active Directory.
Adding Security groups to Microsoft 365 groups.
Adding Microsoft 365 groups to Security groups or other Microsoft 365 groups.
Assigning apps to nested groups.
Applying licenses to nested groups.
Adding distribution groups in nesting scenarios.
Adding security groups as members of mail-enabled security groups

Author: Scott Duffey

memdocs/intune/apps/apps-deploy.md

@@ -96,6 +96,9 @@ The following table lists the various options for *assigning* apps to users and
 
 The app is now assigned to the groups that you selected. For more information about including and excluding app assignments, see [Include and exclude app assignments](apps-inc-exl-assignments.md).
 
+> [!Tip]
+> Intune supports assigning apps to nested groups too. For example, if you assigned an app to the "Enineering Global" group and have "Engineering APAC", "Engineering EMEA" and "Engineering US" nested as child groups, the members of those child groups will also be targeted with the assignment.
+
 ## How conflicts between app intents are resolved
 
 A single group is prevented from being targeted for multiple app assignment intents, however if a user or a device is a member of multiple groups that are each assigned with different intents it will result in a conflict. Creating assignment conflicts for applications is not recommended.