Intune Powershell Runbook TMINUS
Intune Powershell Runbook TMINUS
The purpose of this guide is to provide a powershell runbook for implementing Intune. This guide is
assuming you have the M365 Business License. It can apply to EMS licenses, but some features will not
be covered such as Conditional Access and Windows Autopilot. After you run this powershell script you
will have created:
**Disclaimer**
This guide is meant to provide best practices for policy creation and implementation of Intune. It is
meant to be used as a template, but the policies defined will not be the same in all use cases. You
must access to policies and configuration you will need for your customers environment and make
changes as needed. As a best practice, test all configurations with a pilot group before moving to
broad deployment across an entire organization
Pre-Flight Checklist
Create a group for an Intune Pilot Create different groups if you want to separate out different people
into different Intune Polices.
a. Scroll Down in the 365 Admin Portal and Go to the Device Management Portal
2. Copy and Paste the script from GitHub that I created. Here is the link
3. If you want to modify any of the settings for any of the policies, you can view their respective
lines:
Ex. iOS
4. When you run the commands, you will be prompted for a User principal name. Enter the user
principal name of a global administrator:
5. Next, enter the group you created in the beginning of this document that contains your pilot
users:
6. You will see all the policies, apps, and Terms created. Once complete you will get a new
commandline:
7. When you go back to the Device Admin portal, you will be able to see the policies, profile, apps,
and terms.
Enroll Devices: Windows
a. On the Windows 10 Device, click Start and type Access Work or School
b. Click Connect
g. Back in the Intune Portal, you can go to Device Compliance>Policies>Click on your Windows
Policy (we created earlier in this document)
h. You can click on Device status to see compliance status. Note, it can take some time before the
evaluation will complete. In this case, I see the device I just joined as “Not Evaluated”. We just
must wait for that to complete.
Monitoring
a. Click on this line item and the go to Device Compliance on the next page:
b. Click on Windows as it is our policy
c. Here you can see why the device is out of compliance and take action steps to remediate. In this
case it looks like we just need to finish setting up BitLocker to encrypt the drive:
Enroll Devices: iOS and Android
iOS and Android device enrollment can be completed by downloading the Intune Company Portal app
from the app store or google play store:
a. Users will be walked through a wizard after they enter their Azure AD credentials
b. For a detailed list of the entire user experience, you can follow this support guide from
Microsoft:
Intune
Android
• Common FAQs
• Whether we need to tighten or loosen our policies
• End User Experience for Communications to Broad audience
• Common Troubleshooting Techniques for each platform
After this is complete, we want to create communications to our audience for enrollment:
• Why is this service important?
• What pain points will it help them solve?
• What can end users expect?
• What are the steps to get my device enrolled
Lastly, after we have this pushed out and a target date for deployment, we can go back into the Device
Management Admin Center and begin to add our groups to our policies and profiles:
a. Go to Device Compliance and click on policy you want to add a group to:
b. Go to Assignments and select your groups that you want to apply the policy to. You can do the
same with Device Profiles by going to the Device Configuration section
Conclusion
I hope this article provided you some targeted guidance on creating a runbook for Intune. Any feedback
to improve your experience would be greatly appreciated. I would also like to hear if there is more
content that you would like to see in this guide. Any feedback can be sent to my email below: