<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Learning Microsoft Intune - Medium]]></title>
        <description><![CDATA[Unified Endpoint Management with Intune &amp; the Microsoft 365 product suite - Medium]]></description>
        <link>https://medium.com/learning-mem?source=rss----98dd9d89256a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Learning Microsoft Intune - Medium</title>
            <link>https://medium.com/learning-mem?source=rss----98dd9d89256a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:59:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/learning-mem" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[About Intune Primary User]]></title>
            <link>https://medium.com/learning-mem/about-intune-primary-user-84591ddbb1e?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/84591ddbb1e</guid>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[mdm]]></category>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[wi̇ndows11]]></category>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Sat, 11 Feb 2023 01:00:43 GMT</pubDate>
            <atom:updated>2023-02-11T00:56:16.049Z</atom:updated>
            <content:encoded><![CDATA[<p><em>It’s a new year and I’m trying to develop a new writing habit. I’m calling it my “Friday mail sack” as a nod to a hero of mine, Ned Pyle who once ran the </em><a href="https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/bg-p/AskDS/label-name/ned%20pyle"><em>DSTalk blog</em></a><em> and taught me basically everything I ever knew about Active Directory and Group Policy. If you have a question that should be answered in blog format, please shoot me an </em><a href="/service/mailto:Contact@learningMSIntune.com"><em>email </em></a><em>or </em><a href="https://twitter.com/Scottduf"><em>tweet </em></a><em>me!</em></p><blockquote><strong><em>Question:</em></strong><em> Hey Scott… What is the difference between a Primary User and Enrolled by user in Intune? Are they the same?</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPGGHFUJWneisfUSgerUrw.png" /><figcaption>Screenshot of Intune device blade, highlighting Primary User and Enrolled-by user</figcaption></figure><p><strong>Answer:</strong> The Intune “primary user” and “enrolled by” user properties do different things. While the values usually start out the same, “Enrolled by” is immutable, “Primary” user can change during the device’s lifetime. I will tell a story to explain…</p><h3><strong>“Enrolled by” user</strong></h3><p>For a long time, Intune only had the one property, the Intune “Enrolled by” user. That property gets set during user-driven device MDM enrollment and is 100% immutable. To change it, the device would need to be re-enrolled using the UPN of some other user.</p><p>The property didn&#39;t do a whole lot… It helped you identify devices easier in the portal (for example, searching for a user in the troubleshooting page would yield results for all the devices associated with that user), it also helped for user-targeting scenarios, particularly for iOS and Android mobile devices. The enrolledby user relationship enables you to target a user group with “Scott Duffey” in it and have Intune update policy and apps for all Scott Duffey’s devices. On Azure AD Joined Windows devices, things worked (and still do work) a bit differently since the platform supports logons from multiple users. Assuming the device is Azure AD Joined, it works like this:</p><ul><li><strong>No AAD user is logged on yet</strong> — If there is an MDM check-in session while the computer is sitting at Ctrl+Alt+Delete screen, Windows will only present to Intune the Device’s identity when asking for policy. This will be a device-only context MDM session. That means that only device-group targeted policies and apps will apply, no user policy. Not even if there is an enrolledby or primary user relationship.</li><li><strong>User A is logged on </strong>— Assuming User A is an Azure AD user and has an Intune license, the check-in session will be combined user+device context. That means that all the policy and apps assigned to the device or user (via their group memberships) will apply.</li><li><strong>User B is logged on — </strong>Assuming User A logged off already, User B is free to log on and is treated exactly the same way as User A in terms of which policy and apps will be delivered for them.</li></ul><p>To summarize, Windows MDM doesn&#39;t give two hoots about who the primary user of the device is. When reaching out to Intune and asking for a policy update it will present whatever identities it has on hand and ask for the policy, be it Device Identity or Device + User Identity.</p><p>While Windows MDM happily dealt with multi-user’s, there were two key user self-service scenarios that didn’t work well if more than one AAD user was trying to use the same device:</p><ol><li>Installing available apps from the Intune Company Portal, and</li><li>Recovering Bitlocker keys from Azure AD</li></ol><p><strong>Company Portal and Available apps</strong></p><p>The Company Portal app was restricted to only allow the “enrolled by” user of the device to log in, check device compliance and trigger available app installations. This limitation turned out to be a pretty big problem, especially for EDU customer like schools, who mainly did bulk enrollment using provisioning packages created with the Setup School PC app. It was such a problem because the Intune “EnrolledbyUser” was set as <em>null</em>. There was no way to change the enrolledbyUser property to be the real human that would need to install available apps from the company portal. The same sort of problem was also apparent outside of EDU usage.. for example if you (the IT guy/girl) wanted to impress your boss by setting it up and enrolling it using your own credentials, you’d be stamped as the enrolledby user on it forever. Same deal if you ever tried to use a service account (A Device Enrollment Manager (DEM) account) for bulk provisioning.</p><p><strong>Bitlocker self-service key recovery</strong></p><p>The other thing that happens (outside of Intune) during this whole device setup process is the creation of a device object in Azure AD. A new Azure AD object gets created and set with two properties:</p><ol><li><em>DeviceRegisteredOwner,</em><strong> </strong>and</li><li><em>DeviceRegisteredUser.</em></li></ol><p>You wanna know which user gets set on these? You guessed it.. the user who authenticated to AAD during the setup process (either during the OOBE or later in the settings app). And guess who is allowed to self-service recover the device’s bitlocker key from Azure AD? That’s right, the DeviceRegisteredOwner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJtQlldaW5tWHHYOOL0RYw.png" /><figcaption>Screenshot from myaccount.microsoft.com self-service Bitlocker key recovery</figcaption></figure><h3><strong>Primary User</strong></h3><p>In late 2019 to mid 2020, the Intune team (Yes, I was involved in this project too) added some features to start to address some of these challenges…</p><p>We added the new “Primary User” property to all Intune device objects and made it mutable. We tied many experiences to the Primary User, including the Company Portal and Bitlocker self-service recovery and added a new experience for admins to change the assigned Primary User from one user to another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0p-KMP7ZGGoydVHloUugKw.png" /></figure><p>We connected this “Change primary user” button to the Azure AD device object too, so that changing the Intune primary user would also update the Azure AD Device Registered Owner and Device Registered User , thus unifying portal experiences and controlling bitlocker self-service recovery experiences.</p><p>There are some restrictions that had to be applied to this button. It is disabled in a few situations:</p><ol><li>The button only works for Azure AD Joined (Or Hybrid AADJ) devices. On other enrollment types, the button is disabled.</li><li>The user chosen as primary needs to have an Intune license</li><li>The admin making the change needs permission. We added a permission “Managed Device/Set primary user” for this and added it to some built in roles: Helpdesk Operator, School administrator, and Endpoint Security Manager</li></ol><p>We also made some changes to the Company Portal behavior. The company portal can be used by multiple users on the same device, however you must explicitly set it as “Shared” by removing the primary user. Once you’ve done that the user experience is something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*xM7L1PcKqDwWMUURrv5PSA.png" /><figcaption>Notice the “Shared” tag in the Company Portal experience</figcaption></figure><p>Intune now does a pretty good job of assigning primary user when a device enrolls. Check out the table below for Who and When this gets set:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*UKbGK5W4FAQteTYLDfOmjA.png" /><figcaption>Table of Primary User assignment from Microsoft docs: <a href="https://learn.microsoft.com/en-us/mem/intune/remote-actions/find-primary-user#who-is-assigned-as-the-primary-user">https://learn.microsoft.com/en-us/mem/intune/remote-actions/find-primary-user#who-is-assigned-as-the-primary-user</a></figcaption></figure><h3>Wrap up</h3><p>Well that’s everything I know about the EnrolledBy User and Primary User property in Inune! I gave you some bonus content around Azure AD device /user properties and also some of the things I’ve learned about device check-in context. I hope you find it helpful!</p><p><em>If you have a question that should be answered in blog format, please shoot me an </em><a href="/service/mailto:Contact@learningMSIntune.com"><em>email </em></a><em>or </em><a href="https://twitter.com/Scottduf"><em>tweet </em></a><em>me!</em></p><p><strong>Official Microsoft documentation:</strong></p><ul><li><a href="https://learn.microsoft.com/en-us/mem/intune/remote-actions/find-primary-user">Find the primary user of a Microsoft Intune device.</a></li><li><a href="https://techcommunity.microsoft.com/t5/intune-customer-success/change-the-intune-primary-user-public-preview-now-available/ba-p/1221264">Change the Intune Primary User - Public Preview Now Available</a></li></ul><p><strong>Learn about Intune:</strong></p><p><a href="https://www.learningmsintune.com/">Learning Microsoft Intune</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84591ddbb1e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/about-intune-primary-user-84591ddbb1e">About Intune Primary User</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Azure AD Device Extension Attributes in Microsoft Endpoint Manager]]></title>
            <link>https://medium.com/learning-mem/using-azure-ad-device-extension-attributes-in-microsoft-endpoint-manager-19a3b4c30172?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/19a3b4c30172</guid>
            <category><![CDATA[conditional-access]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[azure-ad]]></category>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Tue, 02 Aug 2022 18:19:10 GMT</pubDate>
            <atom:updated>2022-08-02T18:50:07.949Z</atom:updated>
            <content:encoded><![CDATA[<p>In case you missed it, Azure AD recently released 15 new attributes on Azure AD devices for you to populate and use as you please.</p><p>The two main reasons you’ll want to consider using them are:</p><ol><li><strong>Using as a device filter on Conditional Access Policy.</strong> For example, you could add an attribute for “Super secure developer devices” and then make sure developers can only use those devices to access some cloud app, for example Azure DevOps.</li><li><strong>Using in Dynamic Device groups. </strong>You could bundle up all of those “Super secure developer devices” into an Azure AD group. Once they’re in the group you can use that group for delegating administration and/or policy targeting in Microsoft Endpoint Manager (Intune).</li></ol><h3>Which devices in AAD can have Extension Attributes?</h3><p>All Azure AD device objects have extension Attributes. This includes all platforms (Windows, iOS, Android) and Join Types (Registered, AAD Joined and Hybrid AAD Joined). You can apply extension attributes to both Intune managed and unmanaged devices.</p><p>You might also find it useful to add extension attributes to pre-registered Autopilot device objects, so that they can be placed into a group and be targeted with Policies and Applications before they enroll in Intune.</p><h3><strong>How do you populate AAD device extension attributes?</strong></h3><p>Right now, there is a read-only UI experience in the portal for extension attributes. Similarly, the Azure AD Powershell module does not yet have this capability.</p><p>If you want to edit them, you will need to do it manually using Graph API. Here I’ll show you how to use using Microsoft Graph Explorer:</p><ol><li>Go to <a href="https://developer.microsoft.com/en-us/graph/graph-explorer">Graph Explorer</a></li><li>Sign in with AAD credentials</li><li>View all 15 Extension Attribute values for one of your devices by performing a <strong>GET </strong>on the AAD device ObjectID.</li></ol><pre><a href="https://graph.microsoft.com/v1.0/devices/4256d3b7-d604-495e-ab8c-cbefe50e9435">https://graph.microsoft.com/v1.0/devices/{</a>ObjectID}/extensionAttributes</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yZh-rC9VmelO3fCnREhElw.png" /><figcaption>Use Graph Explorer to view extension attributes on AAD registered devices</figcaption></figure><p><em>Tip: You‘ll find the ObjectID in the AAD Portal. Devices &gt; All Devices &gt; {Device} &gt; ObjectID</em></p><p>4. Now <strong>Patch</strong> the desired values. In this example I’m going to use <strong>Extension Attribute 15</strong> to stamp my <strong>“Super secure developer devices” </strong>tag.</p><p>The request body will look something like this:</p><pre>{</pre><pre>“extensionAttribute15”: “Super secure developer devices”</pre><pre>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mmdky5ZWHo9oaXxYQpGOGA.png" /><figcaption>Use graph explorer to update extension attributes on AAD registered devices</figcaption></figure><p>5. Verify that the value was written by performing another <strong>GET</strong>.</p><pre><a href="https://graph.microsoft.com/v1.0/devices/4256d3b7-d604-495e-ab8c-cbefe50e9435/extensionAttributes">https://graph.microsoft.com/v1.0/devices/{ObjectID}/extensionAttributes</a></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*56ZE5y6fsmyS0y5hTkcvUg.png" /><figcaption>Use graph explorer to view the new extension attribute value</figcaption></figure><h3>How do you create a dynamic device group using Extension Attributes?</h3><p>Go to <a href="https://endpoint.microsoft.com/">Microsoft Endpoint Manager</a> &gt; Groups &gt; New group and create a new dynamic device group. Use the extension attributes as the basis for group membership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c4_Gge4Au2xacawIF_WXRg.png" /><figcaption>Create a dynamic device group based on Extension Attributes</figcaption></figure><h3>How do you create a conditional access policy using Extension Attributes?</h3><p>Go to <a href="https://endpoint.microsoft.com/">Microsoft Endpoint Manager</a> &gt; Endpoint Security &gt; Conditional Access and create a new Conditional Access policy. Under Conditions, Filters for Devices you can select the extension attributes as the basis for including or excluding specific devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fDhfp2pm-THujipe3BvVdA.png" /><figcaption>Create an Azure AD Conditional Access policy with a filter for devices</figcaption></figure><h3>How do you view Device Extension Attributes in the console?</h3><p>You can see an AAD registered device’s extension attributes in the <a href="https://portal.azure.com/#view/Microsoft_AAD_Device">Azure AD Portal</a> or the new <a href="https://entra.microsoft.com/#home">Microsoft Entra portal</a>. These attributes are not currently exposed in the <a href="https://endpoint.microsoft.com/">Microsoft Endpoint Manager</a> portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oMpzdgR8hfA1QF2VaYiTA.png" /><figcaption>View Extension Attributes in Microsoft Entra admin center</figcaption></figure><h3>Where can you learn more?</h3><p>Check out the official Microsoft documentation to learn more about Extension Attributes:</p><p>Extension Attributes:</p><p><a href="https://docs.microsoft.com/en-us/powershell/azure/active-directory/using-extension-attributes-sample?view=azureadps-2.0">Azure AD cmdlets to work with extension attributes</a></p><p>Dynamic Device Groups:</p><p><a href="https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/groups-dynamic-membership#rules-for-devices">Rules for dynamically populated groups membership - Azure AD - Microsoft Entra</a></p><p>Conditional Access Filter for Devices</p><p><a href="https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-condition-filters-for-devices">Filter for devices as a condition in Conditional Access policy - Azure Active Directory - Microsoft Entra</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19a3b4c30172" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/using-azure-ad-device-extension-attributes-in-microsoft-endpoint-manager-19a3b4c30172">Using Azure AD Device Extension Attributes in Microsoft Endpoint Manager</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make iOS web clips open in Edge or Chrome (with Intune)]]></title>
            <link>https://medium.com/learning-mem/how-to-make-ios-web-clips-open-in-edge-or-chrome-a49bd9307976?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/a49bd9307976</guid>
            <category><![CDATA[microsoft-intune-suuport]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[mdm]]></category>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Tue, 17 May 2022 04:48:50 GMT</pubDate>
            <atom:updated>2022-05-17T04:50:34.576Z</atom:updated>
            <content:encoded><![CDATA[<p>Two weeks ago, I went to my first, ever <strong>Midwest Management Summit (MMS)</strong> conference and had a great time. As a Microsoft PM, I spent a lot of time talking to IT admins about a broad range of Microsoft Endpoint Manager topics. Some had questions about product and roadmap and others served me with kindly-put feedback.</p><p>I had a few “How do I do xyz in MEM?” questions too which were fun and kept me on my toes.</p><p>Here is one of the curveball questions I got from Sam Monroe…. which we found a solution for and is worth sharing for others.</p><blockquote><strong>“We have a scenario that requires that our iOS web clips to open in Google Chrome, instead of Safari… Can we do that with MEM?”</strong></blockquote><p>Of course, my first response was “why the heck would you want to do that?” Once we got past that, and that this functionality isn&#39;t natively in the MEM UI, I reached out to my Microsoft Product Manager/ mate and Apple guru Andy for help. To my excitement.. he pointed me to this very important part of Apple’s <a href="https://developer.apple.com/documentation/devicemanagement/webclip">Web Clip documentation</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTMAM3D1FTWZMVfO-E-LVg.png" /><figcaption>TargetApplicationBundleIdentifier from Apple MDM documentation on WebClips.</figcaption></figure><h3><strong>Solution — Deploy a web clip that opens in Chrome (or Edge)</strong></h3><p>So the answer is yes. You can do it using an Intune <strong>Custom Policy. </strong>Here’s how:</p><ol><li>Create a new <strong>Custom configuration profile </strong>for iOS/iPadOS</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9gyfamGdl5ECaq-4Y5rOtw.png" /></figure><p>2. You’ll need to upload an .XML or .MobileConfig file for the custom policy body. You can copy and paste from Apple’s sample or mine below into a text editor and update the bolded parts to change the <strong>Name</strong>, <strong>URL </strong>and <strong>browser </strong>to open in.</p><pre>&lt;plist&gt;<br>&lt;dict&gt;<br> &lt;key&gt;PayloadContent&lt;/key&gt;<br> &lt;array&gt;<br> &lt;dict&gt;<br> &lt;key&gt;FullScreen&lt;/key&gt;<br> &lt;true/&gt;<br> &lt;key&gt;IgnoreManifestScope&lt;/key&gt;<br> &lt;false/&gt;<br> &lt;key&gt;IsRemovable&lt;/key&gt;<br> &lt;true/&gt;<br> &lt;key&gt;Label&lt;/key&gt;<br> &lt;string&gt;<strong>Example</strong>&lt;/string&gt;<br> &lt;key&gt;Precomposed&lt;/key&gt;<br> &lt;false/&gt;<br> &lt;key&gt;URL&lt;/key&gt;<br> &lt;string&gt;<strong>example.com</strong>&lt;/string&gt;<br> &lt;key&gt;TargetApplicationBundleIdentifier&lt;/key&gt;<br> &lt;string&gt;<strong>com.google.chrome</strong>&lt;/string&gt;<br> &lt;key&gt;PayloadIdentifier&lt;/key&gt;<br> &lt;string&gt;com.example.mywebclippayload&lt;/string&gt;<br> &lt;key&gt;PayloadType&lt;/key&gt;<br> &lt;string&gt;com.apple.webClip.managed&lt;/string&gt;<br> &lt;key&gt;PayloadUUID&lt;/key&gt;<br> &lt;string&gt;1d6d6912–708e-441a-9272–526ef05bbe3c&lt;/string&gt;<br> &lt;key&gt;PayloadVersion&lt;/key&gt;<br> &lt;integer&gt;1&lt;/integer&gt;<br> &lt;/dict&gt;<br> &lt;/array&gt;<br> &lt;key&gt;PayloadDisplayName&lt;/key&gt;<br> &lt;string&gt;Web Clip&lt;/string&gt;<br> &lt;key&gt;PayloadIdentifier&lt;/key&gt;<br> &lt;string&gt;com.example.myprofile&lt;/string&gt;<br> &lt;key&gt;PayloadType&lt;/key&gt;<br> &lt;string&gt;Configuration&lt;/string&gt;<br> &lt;key&gt;PayloadUUID&lt;/key&gt;<br> &lt;string&gt;289fc7fc-2870–479d-b30f-8d0592b7ef04&lt;/string&gt;<br> &lt;key&gt;PayloadVersion&lt;/key&gt;<br> &lt;integer&gt;1&lt;/integer&gt;<br>&lt;/dict&gt;<br>&lt;/plist&gt;</pre><blockquote>Tip: If you want to open links in Microsoft Edge instead, use the edge bundle id: <strong>com.microsoft.msedge</strong></blockquote><blockquote>(You might find the bundle ID’s for other browsers on <a href="https://offcornerdev.com/bundleid.html">Bundle ID Finder</a>)</blockquote><p>When you are done, the policy will look something like this -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2iTfVWW3c1MBDPVpDxRPyg.png" /></figure><p>3. Next, assign the policy to a group of users or devices. On MDM sync, users will see the Web Clip appear! One nuance with this deployment seems to be that users are unable to long-press the web clip and move it around.. but hey it works!</p><blockquote><strong>Tip — Don’ t forget to also use Intune to deploy the browser (Edge, Chrome or other) so that the web clip has something to open the link with</strong></blockquote><h3>Conclusion</h3><p>Yes. You can deploy a Web Clip in Intune that forces it to open in a browser other than safari… It’s not perfect but it might be just the workaround you need in a pickle! Let me know if it helps!</p><p>Big thanks to Sam Monroe (@Sam_Rlg) for being the inspiration (and tester) for this solution and blog post!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a49bd9307976" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/how-to-make-ios-web-clips-open-in-edge-or-chrome-a49bd9307976">How to make iOS web clips open in Edge or Chrome (with Intune)</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quickly register an AutoPilot device during OOBE]]></title>
            <link>https://medium.com/learning-mem/quickly-register-an-autopilot-device-during-oobe-1cbca5354712?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/1cbca5354712</guid>
            <category><![CDATA[autopilot]]></category>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Mon, 24 Jan 2022 21:12:35 GMT</pubDate>
            <atom:updated>2022-01-24T21:12:35.316Z</atom:updated>
            <content:encoded><![CDATA[<p>Here is the quick reference on harvesting AutoPilot device ID’s from OOBE using powershell. I created post just so I have a quick reference to copy+paste from whenever I need to do this for testing.</p><ol><li>Shift+F10 to enter command prompt from OOBE</li></ol><p>2. Type</p><pre>Powershell</pre><p>3. Type</p><pre>Install-Script -Name Get-WindowsAutoPilotInfo</pre><pre>Y</pre><pre>Y</pre><pre>Set-ExecutionPolicy bypass</pre><pre>Get-WindowsautoPilotInfo.Ps1 -Online</pre><p>4. Provide credentials for your Azure AD admin account</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ONvubldOGH-yvXG7pUseCQ.png" /></figure><p>5. Wait for the registration to complete and say “All devices sync’d”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cbca5354712" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/quickly-register-an-autopilot-device-during-oobe-1cbca5354712">Quickly register an AutoPilot device during OOBE</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intune MDM Authority: You haven’t enabled device management yet.]]></title>
            <link>https://medium.com/learning-mem/intune-mdm-authority-you-havent-enabled-device-management-yet-56572779935b?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/56572779935b</guid>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[sccm]]></category>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Thu, 16 Dec 2021 18:56:01 GMT</pubDate>
            <atom:updated>2021-12-17T17:32:11.432Z</atom:updated>
            <content:encoded><![CDATA[<p>Seen this message before?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*uCSIF7zX5vec5efFs6TS8w.png" /><figcaption>MDM Authority — You haven’t enabled device management yet notification in the MEM admin center.</figcaption></figure><p>Anyone who has worked with in the Microsoft Endpoint Manager admin center has likely seen this notification pop up at some stage. If you configured custom roles and permissions, your chances are even higher.</p><p><strong>Issue 1 — Permissions</strong></p><p>The root cause is likely related to admin permissions — specifically that the account you signed-in to the portal with is missing a very crucial permission: <strong>Organization \ Read</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvIGOLVwfagKTRSukF4DGA.png" /></figure><p>How to fix?</p><p>The fix is to ensure that all of the admins that use the Microsoft Endpoint Manager admin center have the “organization / read” permission assigned to them — It&#39;s a default permission in the built-in roles but would be easy to miss if you were creating your own custom ones.</p><p><strong>Issue 2 — Unlicensed admin</strong></p><p>To use the MEM Admin center, admins either need to either have an Intune license assigned to their account or have the “Unlicensed admins” feature enabled in the tenant. If this isn&#39;t done, the same MDM authority message can pop-up.</p><p>How to fix?</p><ol><li>Assign an Intune license for the admin, or</li><li>Turn on the “Unlicensed admins” feature. Note — All Intune accounts created before mid 2020 will have this enabled by default. After you do it, any admin who is in the “Admin group” for a role assignment will be allowed to use the portal without this message annoying them.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lk2uJpgz9fYkGvqnM76gFw.png" /></figure><p><strong>Why the funky “MDM Authority” message then?</strong></p><p>The notification message about MDM authority’s is really not very intuitive for the cases I described above — The term MDM Authority is mostly a hang-over from when Intune admins were required to make a choice of “MDM authority” when provisioning a new account. The portal UX was designed in a way that requires read of this setting to customize the experience. Those who worked with Intune longer than a couple years would remember when you actually had an MDM authority choice:</p><ul><li>Intune standalone (admin use the MEM console), or</li><li>SCCM (admin uses the SCCM console)</li></ul><p>Nowadays, for new accounts you really don&#39;t need to worry about this MDM authority nonsense. The MDM authority is automatically set to Intune standalone during account provisioning as the SCCM option has gone away in favor of a better co-management approach.</p><p><strong><em>One additional note for completeness —</em></strong></p><p><em>There is a legitimate happy path to see this message — Although it is rare because in my experience — There is a case where the MDM authority could currently be set to “Office 365” and requires upgrading to Intune Standalone. This happens if you started with adding Office 365 licensing only (no Intune, EMS or M365) to your account and specifically enabled “Basic Mobility and Security” in Office 365. “</em><a href="https://docs.microsoft.com/en-us/microsoft-365/admin/basic-mobility-security/choose-between-basic-mobility-and-security-and-intune?view=o365-worldwide"><em>Basic Mobility and security</em></a><em>” is not really Intune, but uses some common infrastructure. If you later went and bought Intune licenses and went to the MEM admin center you may need to switch using this UX.</em></p><p>Thanks for reading — This was a quick post, but I wanted to share in case folks stumble on this and need a quick answer. In the meantime, I’ll talk to some folks about making this silly little message disappear from the console when it doesn&#39;t apply!</p><ul><li>Scott</li></ul><p>12/17/21 — Updated to add the unlicensed admin reason.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56572779935b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/intune-mdm-authority-you-havent-enabled-device-management-yet-56572779935b">Intune MDM Authority: You haven’t enabled device management yet.</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Endpoint Manager — Ignite November 2021 watch list]]></title>
            <link>https://medium.com/learning-mem/microsoft-endpoint-manager-ignite-november-2021-watch-list-4530af15dc9f?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/4530af15dc9f</guid>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[msignite]]></category>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Tue, 02 Nov 2021 22:20:20 GMT</pubDate>
            <atom:updated>2021-11-02T23:06:46.859Z</atom:updated>
            <content:encoded><![CDATA[<h3>Microsoft Endpoint Manager — Ignite November 2021 watch list</h3><p>This is my watch list for new Microsoft Endpoint Manager on-demand content that has come out this week at the Microsoft Ignite virtual conference. These videos are in no special order and I’ll add some more as they are released for on-demand viewing.</p><blockquote><strong>Update 11/2/21: Microsoft posted an official (and more complete) watch list. I’d recommend starting there:</strong></blockquote><blockquote><a href="https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/microsoft-endpoint-manager-at-microsoft-ignite-2021-november/ba-p/2858124">https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/microsoft-endpoint-manager-at-microsoft-ignite-2021-november/ba-p/2858124</a></blockquote><h3>Microsoft Endpoint Manager Videos:</h3><p><a href="https://techcommunity.microsoft.com/t5/video-hub/microsoft-endpoint-manager-a-deep-dive-on-grouping-targeting-and/ba-p/2911265"><strong>Microsoft Endpoint Manager: A deep dive on grouping, targeting and filtering​</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtea2AOIW6U3ynouqAsMHA.png" /></figure><p><em>Ever deployed a new policy or application in Microsoft Intune and wondered what was going on behind the scenes? Maybe you are kicking off a new Microsoft Endpoint Manager deployment and looking for some practical recommendations on designing for performance and scale. This session covers grouping, targeting and filtering in Microsoft Endpoint Manager. You’ll learn about groups and filters, including the new Filters for devices and apps functionality in Conditional Access.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/managing-android-devices-with-microsoft-endpoint-manager/ba-p/2911195">Managing Android devices with Microsoft Endpoint Manager​</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_t2QTmTAMeN8vXv_JNfuw.png" /></figure><p><em>The Microsoft Intune Android Mobility management solution offers a complete set of Android Enterprise (AE) device management choices. Learn about new and expanded options, including corporate-owned devices with work profile, increased compliance settings, and learn how to modernize the end user experiences and take advantage of superior IT admin tools.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/staying-productive-from-anywhere-and-protecting-your-resources/ba-p/2911221">Staying productive from anywhere and protecting your resources using Microsoft Tunnel​</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9VaRXenIdrG5vhryZm6cgg.png" /></figure><p><em>Microsoft Tunnel keeps your employees productive while they are away from the office, while also keeping your internal resources protected. We’ll share notes from the field on how to best set up your Tunnel environment, check the health of your Tunnel Gateway servers in the Microsoft Endpoint Manager admin center, give updates on merging the Tunnel client with Microsoft Defender for Endpoint, and discuss new options on how to keep your environment up-to-date.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/flexible-paths-to-cloud-management-with-microsoft-endpoint/ba-p/2911203">Flexible paths to cloud management with Microsoft Endpoint Manager​</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kBuL5ia7cEYFxw0n5aalpA.png" /></figure><p><em>Find out what you need to know to easily transition from your current on-premises endpoint management solution to a cloud-connected solution. Learn about how tenant attach and co-management add the power of the cloud to managing Windows and other devices.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/unify-endpoint-security-management-with-microsoft-endpoint/ba-p/2911230">Unify endpoint security management with Microsoft Endpoint Manager</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wk4pkW8liDiFgF3kvnidOA.png" /></figure><p><em>Learn how Microsoft is delivering a best-in-class security and management experience by connecting the power of cloud-based Microsoft Defender Advanced Threat Protection with Microsoft Intune and Configuration Manager. This integration brings SecOps and IT pros together with a connected experience across security and device management, including security baselines, BitLocker encryption, Firewall management and more.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/what-s-new-in-windows-device-configuration-in-microsoft-endpoint/ba-p/2911200">What’s new in Windows device configuration in Microsoft Endpoint Manager</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JnPJohfxfMVhuIAG5Wtlxw.png" /></figure><p><em>Here at Microsoft, we thrive on customer feedback. We’ve made some major improvements to the policy and device configuration space over the past few years based directly on customer feedback. Explore the recent developments in Windows device management with Microsoft Endpoint Manager and find out what you can expect looking forward.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/manage-linux-devices-with-microsoft-endpoint-manager/ba-p/2911262"><strong>Manage Linux devices with Microsoft Endpoint Manager​</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnxMhK30ZEMOpcDIVKxhhA.png" /></figure><p><em>Microsoft Endpoint Manager, Azure Active Directory, and Microsoft Edge have partnered to add device management capabilities for Linux desktops. In this session, we will dive into our management solution for Linux desktops. We are thrilled to show how we are enabling Linux users to be as productive and secure as possible.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/managing-macos-devices-with-microsoft-endpoint-manager/ba-p/2911282"><strong>Managing macOS devices with Microsoft Endpoint Manager​</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZNNpMXqYQxt1TfH2bxIiEg.png" /></figure><p>Check out how Microsoft 365 is redefining modern Mac management in organizations. You will learn about key features we have added this year that makes Mac management in Microsoft Endpoint Manager a breeze.</p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/managing-ios-ipados-devices-with-microsoft-endpoint-manager/ba-p/2911273"><strong>Managing iOS/iPadOS devices with Microsoft Endpoint Manager​</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li5GhtRpZjyBAs8uSjNyHw.png" /></figure><p><em>Get the latest updates to iOS/iPadOS support in Microsoft Endpoint Manager. We’ll highlight some improvements being made to Setup Assistant for Modern Authentication and to User Enrollment, and discuss several other exciting new features!</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/enable-remote-help-scenarios-with-microsoft-endpoint-manager/ba-p/2911349"><strong>Enable remote help scenarios with Microsoft Endpoint Manager</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JzVB9Lkxq33Rw6s8hllcZw.png" /></figure><p><em>Many organizations need new tools to support a full-time remote workforce. Remote users with technical issues on their devices needed immediate help, and in this session, we’ll share a new solution to address this very challenge. Come join us and learn how remote help, a cloud-based remote assistance tool integrated with Microsoft Endpoint Manager allows IT admins to help users quickly and seamlessly on Windows devices.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/cloud-attach-today-cloud-manage-now/ba-p/2908529"><strong>Cloud attach today, cloud manage now</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OLhVzF9Yk8RX4b250iF72w.png" /></figure><p><em>Explore the added value and capabilities of cloud attaching both endpoint and the server side. We dive into various scenarios related to the many clouds attach flows that organizations, and the IT pros that support them, should be taking advantage of.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/getting-to-windows-11-with-windows-update-for-business/ba-p/2908310"><strong>Getting to Windows 11 with Windows Update for Business</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_HiYXF1acpDvvkiEDEA9A.png" /></figure><p><em>Join us to learn how servicing practices apply across Windows 10 and Windows 11, and how the new scheduling and protections features available in Windows Update for Business make it safer and easier to upgrade and update than ever before. We’ll also share a look into how to leverage these features and best practices while upgrading to Windows 11 using Microsoft Intune and other Microsoft tools.</em></p><p><a href="https://techcommunity.microsoft.com/t5/video-hub/commercial-driver-and-firmware-servicing-with-the-windows-update/ba-p/2908502"><strong>Commercial driver and firmware servicing with the Windows Update for Business deployment service</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z53cSN5zon6ZLzFwODP6DA.png" /></figure><p><em>Last March, we announced a new driver and firmware deployment service for commercial organizations. Learn about the quality process Microsoft applies to all drivers and firmware updates published to Windows Update. Explore new report views that will accompany the service, the service roadmap, and, most importantly, how we engage with you for feedback.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4530af15dc9f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/microsoft-endpoint-manager-ignite-november-2021-watch-list-4530af15dc9f">Microsoft Endpoint Manager — Ignite November 2021 watch list</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating dynamic groups and filters for Microsoft devices]]></title>
            <link>https://medium.com/learning-mem/creating-dynamic-groups-and-filters-for-microsoft-devices-427e1a7cdea2?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/427e1a7cdea2</guid>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Fri, 22 Oct 2021 23:11:59 GMT</pubDate>
            <atom:updated>2021-11-10T05:20:42.722Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I put out a <a href="https://medium.com/learning-mem/intune-filter-rules-based-on-os-versions-45d115e28282">helpful cross-platform reference</a> for using the Operating System version property of devices when creating dynamic groups and filters while working with Microsoft Endpoint manager. Since folks found that helpful, I thought I’d add some common filter scenarios for using the <strong>Manufacturer </strong>and <strong>Model </strong>properties on Windows 10 and 11 devices.</p><p>You can either copy the rules from here or use the Github link to copy the latest updated version.</p><blockquote><em>Note: These examples are written for Intune filters. If you want to create dynamic device groups in Azure AD you’ll need to update the property names. Replace </em>device.manufacturer<em> with </em>device.deviceManufacturer<em> and </em>device.model<em> with </em>device.deviceModel<em>.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VxIkWaaOVFQMBp-Eri4WZQ.png" /></figure><p><strong>Surface hub devices </strong>(<a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/model/Windows/Microsoft/Surface%20hub">Copy from github</a>)</p><p>I used the -eq operator and added the three current models of surface hub on the market but you could also get away with -startswith operator to capture them all in a simpler (and more future-proof) way.</p><pre>(device.manufacturer -eq &quot;Microsoft Corporation&quot;)<br>and <br>((device.model -eq &quot;Surface Hub 84&quot;)<br>or (device.model -eq &quot;Surface Hub 55&quot;)<br>or (device.model -eq &quot;Surface Hub 2S&quot;))</pre><p><strong>Hololens devices </strong>(<a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/model/Windows/Microsoft/Hololens">Copy from github</a>)</p><p>In this example, I specified the two models by their explicit model name, but you could make this simpler using -startswith.</p><pre>(device.manufacturer -eq &quot;Microsoft Corporation&quot;) <br>and <br>((device.model -eq &quot;HoloLens 2&quot;) <br>or (device.model -eq &quot;HoloLens&quot;))</pre><p><strong>Hyper-V Virtual machines </strong>(<a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/model/Windows/Microsoft/Hyper-v%20virtual%20machines">Copy from github</a>)</p><pre>(device.manufacturer -eq &quot;Microsoft Corporation&quot;) <br>and (device.model -eq &quot;Virtual Machine&quot;)</pre><p><strong>Windows 365 devices </strong>(<a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/model/Windows/Microsoft/Windows%20365">Copy from github</a>)</p><p>Since all Windows 365 models all start with the word “CloudPC” I used the -startswith operator but you could also use -eq operator if you want to target a specific size device, for example “Cloud PC Enterprise 2vCPU/8GB/128GB”</p><pre>(device.manufacturer -eq &quot;Microsoft Corporation&quot;) <br>and <br>(device.model -startswith &quot;Cloud PC&quot;)</pre><p><strong>Surface Laptops and Desktops </strong>(<a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/model/Windows/Microsoft/Surface%20laptop%20models">Copy from github</a>)</p><p>I could have used the -contains operator for “Surface” in this example but I wanted to make sure it was clear that Surface Studio (not a laptop) would also be included. Adjust it as you see fit :)</p><pre>(device.manufacturer -eq &quot;Microsoft Corporation&quot;) <br>and <br>((device.model -eq &quot;Surface 2&quot;)<br>or (device.model -eq &quot;Surface 3&quot;)<br>or (device.model -startsWith &quot;Surface Book&quot;)<br>or (device.model -startsWith &quot;Surface Go&quot;)<br>or (device.model -startsWith &quot;Surface Laptop&quot;)<br>or (device.model -startsWith &quot;Surface Pro&quot;)<br>or (device.model -startsWith &quot;Surface Studio&quot;))</pre><p>Let me know if these samples help you and I’ll add some more!</p><p>-Scott</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=427e1a7cdea2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/creating-dynamic-groups-and-filters-for-microsoft-devices-427e1a7cdea2">Creating dynamic groups and filters for Microsoft devices</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intune filter rules based on OS versions — Handy reference]]></title>
            <link>https://medium.com/learning-mem/intune-filter-rules-based-on-os-versions-45d115e28282?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/45d115e28282</guid>
            <category><![CDATA[windows-11]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[endpoint-manager]]></category>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Fri, 22 Oct 2021 03:20:44 GMT</pubDate>
            <atom:updated>2021-10-22T03:29:19.903Z</atom:updated>
            <content:encoded><![CDATA[<p>Here is a handy reference if you are trying to create Intune filters for the purpose of targeting only certain operating system versions (or excluding them) from App or policy deployments.</p><p><strong>Steps:</strong></p><ol><li>Remove my comments or use the github link to copy without comments.</li><li>Copy and Paste the relevant sections into the Advanced syntax editor</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*50uxrtZYrUOotraZFlk0Mw.png" /><figcaption>Copy and paste into the Filters rule syntax editor</figcaption></figure><h3>Windows 10 and later</h3><p><strong>Example — All Windows 10 and 11 major versions (</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/Windows/Windows%20Major%20Versions"><strong>copy from github</strong></a><strong>)</strong></p><pre>(device.osVersion -startsWith &quot;10.0.22&quot;) // Windows 11 Original release<br>or (device.osVersion -startsWith &quot;10.0.19043&quot;) // Windows 10 21H1<br>or (device.osVersion -startsWith &quot;10.0.19042&quot;) // Windows 10 20H2<br>or (device.osVersion -startsWith &quot;10.0.19041&quot;) // Windows 10 2004<br>or (device.osVersion -startsWith &quot;10.0.18363&quot;) // Windows 10 1909<br>or (device.osVersion -startsWith &quot;10.0.18362&quot;) // Windows 10 1903<br>or (device.osVersion -startsWith &quot;10.0.17763&quot;) // Windows 10 1809<br>or (device.osVersion -startsWith &quot;10.0.17134&quot;) // Windows 10 1803<br>or (device.osVersion -startsWith &quot;10.0.16299&quot;) // Windows 10 1709<br>or (device.osVersion -startsWith &quot;10.0.15063&quot;) // Windows 10 1703<br>or (device.osVersion -startsWith &quot;10.0.14393&quot;) // Windows 10 1607<br>or (device.osVersion -startsWith &quot;10.0.10586&quot;) // Windows 10 1511<br>or (device.osVersion -startsWith &quot;10.0.10240&quot;) // Windows 10 1507 (RTM)</pre><h3><strong>Android Enterprise</strong></h3><p>There are some differences in how Android devices report their model information to Intune. For example, Work Profile (ie: BYOD) devices report version numbers including a decimal point (eg: “11.0&quot;) but COSU/COBO/COPE, from version 9 and up only show the major version (eg: 11).</p><p>For this reason, If you are targeting a policy for both management types, Id recommend using the <strong>-Startswith </strong>or <strong>-Contains </strong>to make sure you are capturing both.</p><p>Here are a couple of examples</p><p><strong>Example — Target all Android Enterprise by major Android version release (</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/Android/Android%20Enterprise%20Major%20versions"><strong>copy from github</strong></a><strong>)</strong></p><pre>Device.osVersion -startswith (&quot;12&quot;) <br>or Device.osVersion -startswith (&quot;11&quot;)<br>or Device.osVersion -startswith (&quot;10&quot;)<br>or Device.osVersion -startswith (&quot;9&quot;) //Pie<br>or Device.osVersion -startswith (&quot;8&quot;) //Oreo<br>or Device.osVersion -startswith (&quot;7&quot;) //Nougat<br>or Device.osVersion -startswith (&quot;6&quot;) //Marshmallow<br>or Device.osVersion -startswith (&quot;5&quot;) //Lollipop</pre><p><strong>Example — Target all Android Enterprise (COSO, COPE, COSU devices) by using explicit version numbers (</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/Android/Android%20Enterprise%20COSU%2CCOPE%2C%20COBO%20explicit%20versions"><strong>copy from github</strong></a><strong>)</strong></p><pre>Device.osVersion -eq (&quot;12&quot;)<br> or Device.osVersion -eq (&quot;11&quot;)<br> or Device.osVersion -eq (&quot;10&quot;)<br> or Device.osVersion -eq (&quot;9&quot;)<br> or Device.osVersion -eq (&quot;8.1.0&quot;)<br> or Device.osVersion -eq (&quot;8.0.0&quot;)<br> or Device.osVersion -eq (&quot;7.1.2&quot;)<br> or Device.osVersion -eq (&quot;7.1.1&quot;)<br> or Device.osVersion -eq (&quot;7.0&quot;)<br> or Device.osVersion -eq (&quot;6.0.1&quot;)<br> or Device.osVersion -eq (&quot;6.0&quot;)<br> or Device.osVersion -eq (&quot;5.0.2&quot;)<br> or Device.osVersion -eq (&quot;5.1.1&quot;)</pre><p><strong>Example — Target all Android Enterprise (work profile devices) by explicit version (</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/Android/Android%20Enterprise%20Work%20Profile%20explicit%20versions"><strong>copy from github</strong></a><strong>)</strong></p><p><em>(Tip: Notice work profile devices have a period period (.0) for major versions)</em></p><pre>Device.osVersion -eq (&quot;12.0&quot;)<br>or Device.osVersion -eq (&quot;11.0&quot;)<br>or Device.osVersion -eq (&quot;10.0&quot;)<br>or Device.osVersion -eq (&quot;9.0&quot;)<br>or Device.osVersion -eq (&quot;8.1.0&quot;)<br>or Device.osVersion -eq (&quot;8.0.0&quot;)<br>or Device.osVersion -eq (&quot;7.1.2&quot;)<br>or Device.osVersion -eq (&quot;7.1.1&quot;)<br>or Device.osVersion -eq (&quot;7.0&quot;)<br>or Device.osVersion -eq (&quot;6.0.1&quot;)<br>or Device.osVersion -eq (&quot;6.0&quot;)<br>or Device.osVersion -eq (&quot;5.1.1&quot;)<br>or Device.osVersion -eq (&quot;5.1&quot;)<br>or Device.osVersion -eq (&quot;5.0.2&quot;)<br>or Device.osVersion -eq (&quot;5.0.1&quot;)<br>or Device.osVersion -eq (&quot;5.0&quot;)</pre><h3><strong>Android Device Administrator</strong></h3><p>Android DA devices typically show in the Intune console with the full version number string including decimal separating major and minor version. Depending on your requirements you can filter in/out major versions or be explicit about minor versions.</p><p><strong>Example — Target all Android DA by major Android version release (</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/iOS/iOS%20Major%20Versions"><strong>copy from github</strong></a><strong>)</strong></p><pre>Device.osVersion -startswith (&quot;12&quot;) <br>or Device.osVersion -startswith (&quot;11&quot;)<br>or Device.osVersion -startswith (&quot;10&quot;)<br>or Device.osVersion -startswith (&quot;9&quot;) //Pie<br>or Device.osVersion -startswith (&quot;8&quot;) //Oreo<br>or Device.osVersion -startswith (&quot;7&quot;) //Nougat<br>or Device.osVersion -startswith (&quot;6&quot;) //Marshmallow<br>or Device.osVersion -startswith (&quot;5&quot;) //Lollipop<br>or Device.osVersion -startswith (&quot;4&quot;) //Ice Cream Sandwich</pre><p><strong>Example — Target all Android DA by explicit version (c</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/Android/Android%20DA%20Explicit%20versions"><strong>opy from github</strong></a><strong>)</strong></p><pre>Device.osVersion -eq (&quot;12.0&quot;)<br>or Device.osVersion -eq (&quot;11.0&quot;)<br>or Device.osVersion -eq (&quot;10.0&quot;)<br>or Device.osVersion -eq (&quot;9.1&quot;)<br>or Device.osVersion -eq (&quot;9.0&quot;)<br>or Device.osVersion -eq (&quot;8.0.0&quot;)<br>or Device.osVersion -eq (&quot;8.1.0&quot;)<br>or Device.osVersion -eq (&quot;8.1&quot;)<br>or Device.osVersion -eq (&quot;8.0&quot;)<br>or Device.osVersion -eq (&quot;7.1.2&quot;)<br>or Device.osVersion -eq (&quot;7.1&quot;)<br>or Device.osVersion -eq (&quot;7.1.1&quot;)<br>or Device.osVersion -eq (&quot;7.0.0&quot;)<br>or Device.osVersion -eq (&quot;7.0&quot;)<br>or Device.osVersion -eq (&quot;6.1&quot;)<br>or Device.osVersion -eq (&quot;6.0.1&quot;)<br>or Device.osVersion -eq (&quot;6.0&quot;)<br>or Device.osVersion -eq (&quot;5.1.1&quot;)<br>or Device.osVersion -eq (&quot;5.1&quot;)<br>or Device.osVersion -eq (&quot;5.0.2&quot;)<br>or Device.osVersion -eq (&quot;5.0.1&quot;)<br>or Device.osVersion -eq (&quot;5.0&quot;)<br>or Device.osVersion -eq (&quot;4.0&quot;)<br>or Device.osVersion -eq (&quot;4.4.4&quot;)<br>or Device.osVersion -eq (&quot;4.4.2&quot;)<br>or Device.osVersion -eq (&quot;4.2.2&quot;)</pre><h3>iOS / iPadOS</h3><p>iPhones, iPads and iPods seem to be pretty consistent in their use of version numbers. Here is a sample using the -eq operator. I think it makes a lot of sense to use -Startswith when working with iOS/iPad OS versions.</p><p><strong>Example — Target all iOS/iPadOS by major version (</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/iOS/iOS%20Major%20Versions"><strong>copy from github</strong></a><strong>)</strong></p><pre>Device.osVersion -startswith (&quot;15&quot;)<br>or device.osVersion -startswith (&quot;14&quot;)<br>or Device.osVersion -startswith (&quot;13&quot;)<br>or Device.osVersion -startswith (&quot;12&quot;)<br>or Device.osVersion -startswith (&quot;11&quot;)<br>or Device.osVersion -startswith (&quot;10&quot;)<br>or Device.osVersion -startswith (&quot;9&quot;)</pre><p><strong>Example — Target all iOS/iPadOS by explicit version (</strong><a href="https://github.com/Scottduf/Intune-filters-catalog/blob/main/osVersion/iOS/iOS%20Explicit%20versions"><strong>copy from github</strong></a><strong>)</strong></p><pre>device.osVersion -eq (&quot;15.1&quot;) <br> or device.osVersion -eq (&quot;15.0.2&quot;)<br> or device.osVersion -eq (&quot;15.0.1&quot;)<br> or device.osVersion -eq (&quot;15.0&quot;) <br> or device.osVersion -eq (&quot;15.0&quot;)<br> or device.osVersion -eq (&quot;14.8&quot;)<br> or device.osVersion -eq (&quot;14.8&quot;)<br> or device.osVersion -eq (&quot;14.7.1&quot;) <br> or device.osVersion -eq (&quot;14.7.1&quot;)<br> or device.osVersion -eq (&quot;14.7&quot;) <br> or device.osVersion -eq (&quot;14.6&quot;) <br> or device.osVersion -eq (&quot;14.6&quot;) <br> or device.osVersion -eq (&quot;14.5.1&quot;)<br> or device.osVersion -eq (&quot;14.5&quot;) <br> or device.osVersion -eq (&quot;14.4.2&quot;) <br> or device.osVersion -eq (&quot;14.4.2&quot;) <br> or device.osVersion -eq (&quot;14.4.1&quot;) <br> or device.osVersion -eq (&quot;14.4&quot;) <br> or device.osVersion -eq (&quot;14.4&quot;) <br> or device.osVersion -eq (&quot;14.3&quot;) <br> or device.osVersion -eq (&quot;14.2.1&quot;) <br> or device.osVersion -eq (&quot;14.2&quot;) <br> or device.osVersion -eq (&quot;14.1&quot;) <br> or device.osVersion -eq (&quot;14.0.1&quot;) <br> or device.osVersion -eq (&quot;14.0&quot;) <br> or device.osVersion -eq (&quot;13.7&quot;) <br> or device.osVersion -eq (&quot;13.6.1&quot;) <br> or device.osVersion -eq (&quot;13.6&quot;) <br> or device.osVersion -eq (&quot;13.5.5&quot;) <br> or device.osVersion -eq (&quot;13.5.1&quot;) <br> or device.osVersion -eq (&quot;13.5.1&quot;) <br> or device.osVersion -eq (&quot;13.5&quot;) <br> or device.osVersion -eq (&quot;13.4.5&quot;) <br> or device.osVersion -eq (&quot;13.4.1&quot;) <br> or device.osVersion -eq (&quot;13.4&quot;) <br> or device.osVersion -eq (&quot;13.3.1&quot;) <br> or device.osVersion -eq (&quot;13.3&quot;) <br> or device.osVersion -eq (&quot;13.2.3&quot;) <br> or device.osVersion -eq (&quot;13.2.2&quot;) <br> or device.osVersion -eq (&quot;13.2&quot;) <br> or device.osVersion -eq (&quot;13.1.3&quot;) <br> or device.osVersion -eq (&quot;13.1.2&quot;) <br> or device.osVersion -eq (&quot;13.1.1&quot;) <br> or device.osVersion -eq (&quot;13.1&quot;) <br> or device.osVersion -eq (&quot;13.0&quot;) <br> or device.osVersion -eq (&quot;12.5.5&quot;) <br> or device.osVersion -eq (&quot;12.5.4&quot;) <br> or device.osVersion -eq (&quot;12.5.3&quot;) <br> or device.osVersion -eq (&quot;12.5.2&quot;) <br> or device.osVersion -eq (&quot;12.5.1&quot;) <br> or device.osVersion -eq (&quot;12.5&quot;) <br> or device.osVersion -eq (&quot;12.4.9&quot;) <br> or device.osVersion -eq (&quot;12.4.8&quot;) <br> or device.osVersion -eq (&quot;12.4.7&quot;) <br> or device.osVersion -eq (&quot;12.4.6&quot;) <br> or device.osVersion -eq (&quot;12.4.5&quot;) <br> or device.osVersion -eq (&quot;12.4.4&quot;) <br> or device.osVersion -eq (&quot;12.4.3&quot;) <br> or device.osVersion -eq (&quot;12.4.2&quot;) <br> or device.osVersion -eq (&quot;12.4.1&quot;) <br> or device.osVersion -eq (&quot;12.4&quot;) <br> or device.osVersion -eq (&quot;12.3.2&quot;) <br> or device.osVersion -eq (&quot;12.3.1&quot;) <br> or device.osVersion -eq (&quot;12.3&quot;) <br> or device.osVersion -eq (&quot;12.2&quot;) <br> or device.osVersion -eq (&quot;12.1.4&quot;) <br> or device.osVersion -eq (&quot;12.1.3&quot;) <br> or device.osVersion -eq (&quot;12.1.2&quot;) <br> or device.osVersion -eq (&quot;12.1.1&quot;) <br> or device.osVersion -eq (&quot;12.1&quot;) <br> or device.osVersion -eq (&quot;12.0.1&quot;) <br> or device.osVersion -eq (&quot;12.0&quot;) <br> or device.osVersion -eq (&quot;11.4.1&quot;) <br> or device.osVersion -eq (&quot;11.4&quot;) <br> or device.osVersion -eq (&quot;11.3.1&quot;) <br> or device.osVersion -eq (&quot;11.3&quot;) <br> or device.osVersion -eq (&quot;11.2.6&quot;) <br> or device.osVersion -eq (&quot;11.2.5&quot;) <br> or device.osVersion -eq (&quot;11.2.2&quot;) <br> or device.osVersion -eq (&quot;11.2.1&quot;) <br> or device.osVersion -eq (&quot;11.2&quot;) <br> or device.osVersion -eq (&quot;11.1.2&quot;) <br> or device.osVersion -eq (&quot;11.1.1&quot;) <br> or device.osVersion -eq (&quot;11.1&quot;) <br> or device.osVersion -eq (&quot;11.0.3&quot;) <br> or device.osVersion -eq (&quot;11.0.2&quot;) <br> or device.osVersion -eq (&quot;11.0.1&quot;) <br> or device.osVersion -eq (&quot;11.0&quot;) <br> or device.osVersion -eq (&quot;10.3.4&quot;) <br> or device.osVersion -eq (&quot;10.3.3&quot;) <br> or device.osVersion -eq (&quot;10.3.2&quot;) <br> or device.osVersion -eq (&quot;10.3.1&quot;) <br> or device.osVersion -eq (&quot;10.3&quot;) <br> or device.osVersion -eq (&quot;10.3&quot;) <br> or device.osVersion -eq (&quot;10.2.1&quot;) <br> or device.osVersion -eq (&quot;10.2&quot;) <br> or device.osVersion -eq (&quot;10.1.1&quot;) <br> or device.osVersion -eq (&quot;10.0.2&quot;) <br> or device.osVersion -eq (&quot;10.0.1&quot;) <br> or device.osVersion -eq (&quot;9.3.6&quot;) <br> or device.osVersion -eq (&quot;9.3.5&quot;) <br> or device.osVersion -eq (&quot;9.3.4&quot;) <br> or device.osVersion -eq (&quot;9.3.3&quot;) <br> or device.osVersion -eq (&quot;9.3.2&quot;) <br> or device.osVersion -eq (&quot;9.3.1&quot;) <br> or device.osVersion -eq (&quot;9.2.1&quot;) <br> or device.osVersion -eq (&quot;9.2&quot;) <br> or device.osVersion -eq (&quot;9.1&quot;) <br> or device.osVersion -eq (&quot;8.4.1&quot;) <br> or device.osVersion -eq (&quot;8.4&quot;) <br> or device.osVersion -eq (&quot;8.3&quot;)</pre><p>If you are new to Filters in Microsoft Endpoint Manager — I suggest reading the Microsoft docs : <a href="https://docs.microsoft.com/en-us/mem/intune/fundamentals/filters">https://docs.microsoft.com/en-us/mem/intune/fundamentals/filters</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45d115e28282" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/intune-filter-rules-based-on-os-versions-45d115e28282">Intune filter rules based on OS versions — Handy reference</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Set up Azure AD Certificate-Based Authentication for Office Apps on Mobile Devices (IOS and…]]></title>
            <link>https://medium.com/learning-mem/how-to-set-up-azure-ad-certificate-based-authentication-for-office-apps-on-mobile-devices-ios-and-73f42d476c95?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/73f42d476c95</guid>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Mon, 22 Mar 2021 02:33:06 GMT</pubDate>
            <atom:updated>2021-03-22T02:33:05.990Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Set up Azure AD Certificate-Based Authentication for Office Apps on Mobile Devices (IOS and Android) PART 4</h3><p>This is the last part of this blog series and is focussed on getting some user certificates to your devices and testing that certificate authentication works for the office apps. To get to this point you should have Published a CRL, Setup Azure AD and configured ADFS).<br>There are a number of ways to deploy certificates to Mobile devices. The most common way for enterprises to do it is to configure Intune (or another MDM product) with certificate profiles (PFX or SCEP) so that once the device is enrolled, the user automatically gets a certificate created for them on that device. There are tonnes of good resources out there already showing you how to <a href="https://manage.microsoft.com/MicrosoftIntune/Home?accountid=43a5770e-756f-466c-bf6b-8a170ad3fa42">setup it</a> up so here I’m just going to focus on getting the certificate template right. For the most part, you don’t need MDM to test this out (With the exception of iOS — because its difficult to get a root CA cert installed any other way). In this post, I’ll cover the process for testing without MDM — by manually requesting a cert from a domain joined windows machine, then copy it) but when I get to testing on iOS devices I do eventually fallback to Intune for distributing the RootCA cert to iOS.</p><ol><li>On your CA server, open <strong>Certification Authority</strong>, right-click <strong>Certificate Templates</strong>, <strong>Manage</strong>.</li><li>Create a new certificate template with the following key properties: (Tip: Duplicate and adjust the USER template)</li><li><strong>Subject Name:</strong> Supply in the Request</li><li><strong>EKU:</strong> Client Authentication</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/0*effSpWSAm86LOu3o.png" /></figure><p>3. Apply, then close the certificate template console<br>4. Right click <strong>Certificate Templates</strong>, <strong>New</strong>, <strong>Certificate Template to issue </strong><br>5. Select the template you just created. And <strong>Ok.</strong></p><p><strong>Testing from Internal domain-joined Windows Device</strong></p><p>6. Log onto a domain-joined windows client machine with a test user account, run <strong>certmgr.msc</strong><br>7. Expand <strong>Personal</strong>, <strong>Certificates</strong>, Right click <strong>All tasks</strong>, <strong>request new certificate</strong><br>8. Next, Next through the wizard til you get to the <strong>Request Certificates page</strong>, Select <strong>Properties</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/0*5hCo6vmW-pGOSoZa.png" /></figure><p>9. Add details for the Subject Name and Subject Alternative Name (We specified “Supply in Request” in the certificate template):</p><ul><li><strong>SubjectName:</strong> Common Name</li><li><strong>Alternative Name</strong>: User Principal Name or Email (Whichever matches your users identities in AAD)</li></ul><p><em>Note 1: iOS doesn’t support fully distinguished name as the subject name format or including e-mail address in subject name<br></em> <em>Note 2: For iOS to support with Exchange ActiveSync clients, The email (RFC822) attribute must match the user’s routable email address in Exchange Online. If the RFC822 attribute is not present, the UPN attribute of the certificate must match the UPN of the user in Azure AD. This is required to map the certificate to a user in Azure AD.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/0*NGTOcXArAeszRAyG.png" /></figure><p>10. Apply, then click <strong>Enrol </strong>to complete the ce</p><p>rtificate request. You should now see the user certificate in the Personal Store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vnCgwBxrSuT1B6sz.png" /></figure><p>11. Now that you have a certificate on one of your domain joined machines, test it out. Go to <a href="https://portal.office.com/">https://portal.office.com</a> , Choose <strong>Sign in with a certificate</strong> option and see if it allows you to login.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*qbkADj1VapQG1LLS.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/0*euGw3xOeIJO1Vpam.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/0*qvYYPKVYk8YFOBDn.png" /></figure><p>Tip: If this fails, check your client can connect to your WAP server on port 49443. If it still isnt working, Take a look at the CAPI2 event log ( Windows Event Viewer, Applications and Services Log, Microsoft, Windows, CAPI2) on your WAP server. Enable the log if it isnt already. This will bubble up any issues with the certificate chain or CRL. <strong>Testing from an External Windows Device</strong></p><p>12. It’s a good idea to test the same steps above from a Windows client external from your network to make sure the whole Web Application Proxy (WAP) part is right and ports are configured properly. To do that, go back to <strong>certmgr.msc</strong> and export the user certificate along with the private key (The certificate has to be maked as exportable in the template we created earlier). Copy the .pfx over to your external test Windows devices, import the User Cert (the RootCA will automatically be put into the Trusted Root Certificate Authority Store) and try the steps above.</p><p>If you have a version of android that doesn’t have <strong>Testing on an Android Device (7.0)</strong> <br>13. Drop the same user cert (pfx) onto your android (connect it via usb, memory card, etc).<br>14. Select the user .pfx file and you will be prompted to provide a friendly name for the certificate and install. Accept the default name and click ok.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/0*MAQqa10FUCQbkugA.jpg" /></figure><p>15. To check the certs are installed correctly, go to <strong>Settings</strong>, <strong>Lock Screen and Security</strong>, <strong>Other Security Settings</strong>, <strong>User Certificates</strong>. You should see both the CA and User Cert listed.<br><strong>User Certificates</strong> in the settings menu, another trick to find what certificates are installed is to go to “Network Connections” (for knox devices) or “Settings (Wireless &amp; networks)” (for non-knox). Then go to More &gt; VPN &gt; + add &gt; Type = L2TP/IPSec RSA (or any RSA related selections) the drop down for “IP Sec User Certificates” will show a list of User Certs installed on the device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/0*-0wrglc0LpSQc_0N.png" /></figure><p>16. Test out browser access first. Head to <a href="https://portal.office.com/">https://portal.office.com</a>, put in the users UPN and wait for the redirection to your ADFS page. Click “ <strong>Use a Certificate” </strong>and you should be logged on.<br>17. If all that works, download OneDrive ( <a href="https://docs.microsoft.com/en-us/azure/active-directory/active-directory-certificate-based-authentication-android">or one of the other supported apps</a>), and test the sign-in and certificate authentication flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/0*5J2uwR8opik0BgQm.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/0*KcmOgQgCY5P4yDC4.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/0*XqFlX6Zz54rOlhdn.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/0*QmkmRipGD_5rjaCg.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/0*TD6cSUidoskqzuHe.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/0*FPnamf5nGhTtYIlT.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/0*Uuu0fCmBZO-V7C3-.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/0*rLrLO1jAESe2rcnX.png" /></figure><p><strong>Testing on an iOS Device</strong></p><p>18. For iOS, Email the same .PFX user certificate to yourself and install it on the device. The problem is that the certificate is “not verified” under the certificate profile. The RootCA is not installed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/0*-W4TVQ23jFhrpBJa.png" /></figure><p>19. The only way that I know to get the RootCA installed is through MDM or via the Apple Configurator tool (can only be installed on Mac OS). Because I don’t own a Macbook, I’ll create a Trusted CA certificate profile in Intune and deploy it (Screenshots below are for how to create this profile if using Intune Hybrid or Standalone mode respectively):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/0*95kzUHVPBQ2uHDnp.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/0*emtDm7_KEUHaXdcd.png" /></figure><p>20. After you have enrolled the device in Intune through the company portal, the RootCA will be deployed, the PFX certificate that you copied earlier will now say <strong>Verified.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*UjxwYlGOh9gs6jd6.png" /></figure><p>21. Install the Authenticator App from the store (This is necessary for iOS but not android)<br>22. Test to see if it works by installing Outlook (or onedrive/word/excel/powerpoint) and walking through the sign-in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/0*IePsbZcSiBg2S53U.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*Kl05cM-qewkx4jV8.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*7WOE3etVtT5nDco3.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*rfvJC3pVJHtKFmzp.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/0*_UDLNOsVjMd5mP_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*CN9najxp7BstPmYj.png" /></figure><p><em>Originally published at </em><a href="https://microscott.azurewebsites.net/2017/03/30/how-to-set-up-azure-ad-certificate-based-authentication-for-office-apps-on-mobile-devices-ios-and-android-part-4/"><em>https://microscott.azurewebsites.net</em></a><em> on March 30, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73f42d476c95" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/how-to-set-up-azure-ad-certificate-based-authentication-for-office-apps-on-mobile-devices-ios-and-73f42d476c95">How to Set up Azure AD Certificate-Based Authentication for Office Apps on Mobile Devices (IOS and…</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Set up Azure AD Certificate-Based Authentication for Office Apps on Mobile Devices (iOS and…]]></title>
            <link>https://medium.com/learning-mem/how-to-set-up-azure-ad-certificate-based-authentication-for-office-apps-on-mobile-devices-ios-and-89b32cff6b4?source=rss----98dd9d89256a---4</link>
            <guid isPermaLink="false">https://medium.com/p/89b32cff6b4</guid>
            <dc:creator><![CDATA[Scott Duffey]]></dc:creator>
            <pubDate>Mon, 22 Mar 2021 02:32:44 GMT</pubDate>
            <atom:updated>2021-03-22T02:32:43.886Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Set up Azure AD Certificate-Based Authentication for Office Apps on Mobile Devices (iOS and Android) — PART 3</h3><p>Active Directory Federation Services is a key requirement in making this solution work. You’ll need to configure some claims ( <strong>serial Number</strong> and <strong>Issuer</strong>) so that they are issued to users and eventually presented to Azure AD. You also need to make the <strong>“Sign in using an X.509 certificate”</strong> option available at your ADFS logon page. By this stage, you should have an externally reachable CRL and Setup Azure AD for cert-based auth. Make sure you have done that — See Part1 and Part2 of this series.</p><ol><li>On your ADFS Server, Go to <strong>Claims Provider Trusts</strong>, Select <strong>Active Directory</strong> and <strong>Edit Claims Rules</strong>.</li><li>Click <strong>Add Rule, Pass through or Filter an incoming Claim</strong></li><li>Give the rule a Name like <strong>“Certificate Serial Number” and</strong> select <strong>Serial Number </strong>from the drop down and <strong>Finish</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/0*-EEFP0dMi9iOAOlN.png" /></figure><ol><li>Click <strong>Add Rule, </strong>Give it a name like <strong>“Issuer” </strong>and select <strong>Issue </strong>from the drop down menu.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/0*NvUvA4xe28wiyYPg.png" /></figure><ol><li>Now Go to <strong>Relying Party Trust</strong>, <strong>Microsoft Office 365 Identity Platform</strong>, right click and select edit claims rules</li><li>On the <strong>Issuance Transform Rules</strong> tab, select <strong>Add Rule</strong></li><li>Choose <strong>Pass Through or Filter an Incoming Claim </strong>and add both the<strong> Serial</strong> and <strong>Issuer</strong> claim as was done for Active Directory in the last step.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/0*pfB_yF5dBoDVsyus.png" /></figure><ol><li>Now to add the Certificate sign-in option, go to <strong>Authentication Policies </strong>and <strong>Edit </strong>the primary authentication options.</li><li>Enable <strong>Certificate Authentication </strong>(I’m enabling it for internal and External access so I can test this easily on my internal clients first)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/0*yopjo4E9lSMEgXbS.png" /></figure><ol><li>Test by going to portal.office.com, enter a username.domain.com and you are redirected to your ADFS Sign-in page. Notice that there is now a certificate option to sign-in. (Good idea to test internally and from the internet)</li></ol><p>TIP: The default Text says ( <strong>“Sign in using an X.509 certificate”)</strong> which isn’t that user friendly. You can customise it by running some powershell on the ADFS server:</p><p>Set-AdfsAuthenticationProviderWebContent -Name CertificateAuthentication -DisplayName “Sign in with a certificate”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gq7F-0duWYIg8_7U.png" /></figure><p>(Ignore my customised Sign-in message in the above screenshot — it’s a left over from another configuration)</p><p>11. Make sure that the RootCA certificate exists in the <strong>Trusted Root Certification Authorities </strong>store on both your ADFS Server and WAP server. If it isn’t, copy it over and import it into the machine store. Double-check that you can access the CRL from both servers (Certutil -verify -urlfetch).<br>12. Also, The certificate requests are going to come from the external devices and hit your WAP server on port 49443, If you have some sort of load balancer or external firewall in-front of WAP, make sure its configured to allow this port. The internal requests will hit your ADFS server, so make sure that’s allowed too. A good way to check this is by running PowerShell:</p><p>13. That’s the ADFS bit complete. Now you just need to get a certificate onto some devices to test it out. Head over to Part 4.</p><p><em>Originally published at </em><a href="https://microscott.azurewebsites.net/2017/03/30/how-to-set-up-azure-ad-certificate-based-authentication-for-office-apps-on-mobile-devices-ios-and-android-part-3/"><em>https://microscott.azurewebsites.net</em></a><em> on March 30, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89b32cff6b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/learning-mem/how-to-set-up-azure-ad-certificate-based-authentication-for-office-apps-on-mobile-devices-ios-and-89b32cff6b4">How to Set up Azure AD Certificate-Based Authentication for Office Apps on Mobile Devices (iOS and…</a> was originally published in <a href="https://medium.com/learning-mem">Learning Microsoft Intune</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>