Category Archives: Intune

Configure Azure AD Terms of Use functionality within conditional access in Microsoft Intune

The Azure AD terms of use functionality have been recently upgraded. In this article we will have a look at configuring the Azure Azure AD terms of use functionality for Microsoft Intune while enrolling the devices.

Navigate to Terms of use at https://aka.ms/catou

Search for Conditional Access – Terms of Use – Click on terms of use – Select New Terms

Create a new terms of use. Here we have an option to upload our own company terms of use PDF. There is an option to choose the language format for the terms of use.

Following features can be enabled :

Require users to expand the terms of use – The end users will be required to view the terms of use prior to accepting.

Require users to consent of every device – The end users will be required to consent to the terms of use on every device.

Expire Consents – The terms of use will be enforced immediately and all users will be forced to re-consent on a schedule.

Duration before re-acceptance required (days) –The terms of use will be enforced immediately and each user will have to re-consent every specified number of days.

Once after completed this terms of use needs to be applied to conditional access as per the requirement.

We have 4 options at this moment:

Access to cloud apps for all guests- A conditional access policy will be created for all guests and all cloud apps. This policy impacts the Azure portal. Once this is created, you might be required to sign-out and sign-in.
Access to cloud apps for all users- A conditional access policy will be created for all users and all cloud apps. This policy impacts the Azure portal. Once this is created, you will be required to sign-out and sign-in.
Custom policy- Select the users, groups, and apps that this Terms of Use will be applied to.
Create conditional access policy later- This terms of use will appear in the grant control list when creating a conditional access policy.

Its strongly recommended to go with custom policy or create conditional access policy later option, since the former 2 options will apply for all users accessing all cloud apps and we might have lot of segregation based on user departments, job roles and terms of use might vary for every department.

After created we can see the terms of use created below in the terms of use section.

Further navigation we can see the number of people accepted and declined the terms of use, details and languages.

In the audit logs we can see the actions initiated and changed to the terms of use policy.

Enabling the Terms of use to conditional access intune:

Once after creating the terms of use and selecting the required conditional access template we can see that the new policy that we created will be visible in our CA policy. We can select this option and this will be enforced to all users to accept the terms of policy.

Now we need to select this option to Microsoft Intune device enrollment.

After this is enabled we can run the what if and see if its working for the targeted user. In our case we can see the policy that we enforced is getting applied below.

Client User Behavior- Android Device Enrollment through conditional access policy.

We can see that the Exchange Query IT policy terms of use is applied during device enrollment from android device in our case.

On expanding we can see that the term detail as per the company policy.

Note:

  1. Its always better to roll out this policy to pilot users at the initial stage, verify the behavior and later plan this roll out in a phased approach for remaining users
  2. The IT policy terms can be added for different languages as well based on the different geographic locations.
  3. We have an option to review the users who have accepted the policy and rejected from the policy tab.
  4. Conditional access policy controls (including Terms of use) do not support enforcement on service accounts. So ensure that all the service accounts are excluded.
  5. End user accounts consuming this service will require Azure AD Premium P1, P2, EMS E3, or EMS E5 subscription inorder to activate this service to them.

Thanks & Regards

Sathish Veerapandian

Configure Microsoft Intune to secure office 365 apps in Mobile Devices

Microsoft intune is a  cloud service which was introduced in office365. This intune service is charged per user license. It can be configured for cloud only users as well as hybrid users.

Intune can be used for end users end point protection, MDM ,MAM ,application distributed storage, software license inventory reports , hardware inventory reports , mobile device app publishing, security monitoring.

This blog focuses only  on configuring the in tune  MDM\MAM for cloud only users to secure the office 365 services configured in mobile devices.Using this we would be able to enroll Mobile devices, manage devices and applications, protect the corporate data and retire them when required.

First thing is to see the license required for intune to assign them to end users.

Get-MsolAccountSku

Untitled

We need to see the MDM user Scope set in the azure portal.

https://portal.azure.com

By default it is not set to any users. We can create a group and assign the scope to the group. This will perform the MDM enrollment for Android, iOS devices.

Here we have three URL’s:

  1. MDM/MAM Terms of use – Can be used to set company terms of use.
  2. MDM/MAM discovery URL – This is the device enrollment URL.By default it is set to office 365 enrollment url and can leave them as it is if you are using only intune as MDM/MAM service.
  3. MDM/MAM Compliance URL– URL to be used to give more information to users on why the device  is non-compliant if it doesn’t meet the standards.

All the above options can be customized based or left blank based on the current MDM/MAM setup. If we are rolling out the MDM/MAM first time for all users then we can leave these url’s as default and can update only the terms of use and compliance url as per the company’s security policy.

Untitled2

Now we need to create  below policies:

  1. Device Compliance Policy –To manage compliance for IOS & Android devices.
  2. Device Management policy- for IOS and Android device management.
  3. App Protection policy-Can be created to protect targeted apps only.
  4. Client Apps – Can be used to assign curated managed apps, such as Office 365 apps, to iOS and Android devices
  5. Create one Conditional Access Policy for MDM (Optional)–  Can be enforced to use only Outlook for IOS Andriod, restrict logins from geo locations.

Create Device Compliance Policy-

We need to navigate to the https://portal.office.com – Admin – Select Microsoft Intune and navigate to intune blade

Untitled5

We need to create compliance policy for Android and IOS devices.Example below for Android where the minimum version is 7.1 and blocking rooted devices can be done.

Untitled6

Compliance policies conditions and actions can be created based on the requirement.

Create Configuration Policy:

Configuration policies can be created for Android, Android Enterprise and IOS  in our case , since we are focusing only on configuring the MDM for mobile devices.

Untitled4

Example of creating one configuration  policy for Android devices and restrictions that can be applied to secure corporate data like disable  screen capture, copy paste.

Untitled3

App Protection Policy:.

The app protection policy can be used to protect  and enforce policy only on selective apps. This helps the admins to control only the corporate data even on BYOD devices.

Untitled7

 

Targeted apps can be selected here we can select only required corporate apps.

Untitled8

We have policy settings which can be controlled for the apps installed on the mobile phone.

Example we have an option to choose which storage can be enforced to end users to save the data. These restrictions are applicable only for the targeted apps which we have selected in the previous section.

 

Untitled9

Further sign in security requirements can be controlled based on Device Manufacturers, Pin Attempts etc..,

Untitled10.png

 

Create Client Apps:

Also Intune Client apps can be assigned Android/IOS to end users through intune company portal.

Example one created for publishing VLC player in the Intune Company portal for Android Users.

Untitled21.png

Once applied end user can see this apps  from the android device from the Intune Company Portal App.

Conditional Access Policy  for MDM can be created like below:

Select apps – Create one only for Exchange Online

Untitled19

Login location can be set from where the user access can be controlled based on physical location.

Untitled18

Required approved client app only can be selected.

Untitled20

List of Intune enrolled devices can be seen.

Untitled17

When drill down further it would show all the installed apps in  the discovered apps section.

Untitled16

Further we can see the device compliance status. In below case my device is compliant except for the password which i did not configure as per the password policy set for Android devices.

Untitled23

From the client side in Android device user needs to download the company portal to access all Intune features.

  1. Example VLC app which we published from Client apps for end users.
  2. If the device is not meeting the compliance requirements we get the alert on devices tab.
  3. We get the user warning when the user configures the email.

WhatsApp Image 2018-10-25 at 14.29.37WhatsApp Image 2018-10-25 at 14.33.34WhatsApp Image 2018-10-25 at 14.33.34 (1)

Notes:

  1. This blog gives an overview of how to start enrolling mobile devices through Intune for Office 365 Apps. There are more options available in intune for MDM\MAM and these have to be configured based on the  requirement.
  2. If there are currently any MDM solution in place we need to analyze the current user experience provided to the end users and provide the same or enhance more than the current one.
  3. Its always recommended to test all these features in staging domain evaluate the results before moving into production
  4. Best recommended to roll out the MDM intune only for few pilot test users in beginning and later perform a staged roll outs  based on the  end user  responses.
%d bloggers like this: