<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Intune integration issues in the last week in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/intune-integration-issues-in-the-last-week/m-p/3902168#M470825</link>
    <description>&lt;P&gt;Yes. we are aware of the changes by MS and there is a known issue where the&amp;nbsp; auto-discovery url&amp;nbsp; would not accept .com address.&lt;/P&gt;
&lt;P&gt;Can you share the TAC case with me so that I can understand if there are more such changes&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 02 Aug 2019 16:04:19 GMT</pubDate>
    <dc:creator>Nidhi</dc:creator>
    <dc:date>2019-08-02T16:04:19Z</dc:date>
    <item>
      <title>Intune integration issues in the last week</title>
      <link>https://community.cisco.com/t5/network-access-control/intune-integration-issues-in-the-last-week/m-p/3901482#M470819</link>
      <description>&lt;P&gt;Has anyone else has issues with ISE instances authenticating to Microsoft Intune for external MDM checks starting 7/26? I have a TAC case open but no clear resolution yet.&amp;nbsp; We did notice Microsoft posted a change notice for July 26 and that is exactly when our integration stopped working reliably:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-breaking-changes#app-only-tokens-for-single-tenant-applications-are-only-issued-if-the-client-app-exists-in-the-resource-tenant" target="_blank" rel="noopener"&gt;https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-breaking-changes#app-only-tokens-for-single-tenant-applications-are-only-issued-if-the-client-app-exists-in-the-resource-tenant&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I haven't yet fully parsed all this but it looks like potentially the API ISE uses for queries has changed it's permissions requirements within Azure AD, so I'm posting this to the community since this could affect other ISE installs.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically the symptoms are the ISE event logs are full of "401 Unauthorized" error messages and the external MDM report is showing that the API is not pulling any endpoint data.&amp;nbsp; Is anyone else that uses Intune seeing similar behavior?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 14:02:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/intune-integration-issues-in-the-last-week/m-p/3901482#M470819</guid>
      <dc:creator>packetplumber9</dc:creator>
      <dc:date>2019-08-01T14:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: Intune integration issues in the last week</title>
      <link>https://community.cisco.com/t5/network-access-control/intune-integration-issues-in-the-last-week/m-p/3902168#M470825</link>
      <description>&lt;P&gt;Yes. we are aware of the changes by MS and there is a known issue where the&amp;nbsp; auto-discovery url&amp;nbsp; would not accept .com address.&lt;/P&gt;
&lt;P&gt;Can you share the TAC case with me so that I can understand if there are more such changes&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 16:04:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/intune-integration-issues-in-the-last-week/m-p/3902168#M470825</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2019-08-02T16:04:19Z</dc:date>
    </item>
  </channel>
</rss>

