<?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 WiFi profile in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965235#M263364</link>
    <description>&lt;P&gt;hello&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we have an install with an ISE integration to MS Intune&amp;nbsp;&lt;/P&gt;
&lt;P&gt;would it be possible to use variables in the WiFi profiles to point to Intune and bypass the ISE platform ?&lt;/P&gt;</description>
    <pubDate>Thu, 23 Nov 2023 19:44:52 GMT</pubDate>
    <dc:creator>stephenstown20</dc:creator>
    <dc:date>2023-11-23T19:44:52Z</dc:date>
    <item>
      <title>WiFi profile</title>
      <link>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965235#M263364</link>
      <description>&lt;P&gt;hello&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we have an install with an ISE integration to MS Intune&amp;nbsp;&lt;/P&gt;
&lt;P&gt;would it be possible to use variables in the WiFi profiles to point to Intune and bypass the ISE platform ?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Nov 2023 19:44:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965235#M263364</guid>
      <dc:creator>stephenstown20</dc:creator>
      <dc:date>2023-11-23T19:44:52Z</dc:date>
    </item>
    <item>
      <title>Re: WiFi profile</title>
      <link>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965277#M263370</link>
      <description>&lt;P&gt;What exactly are you trying to achieve?&lt;/P&gt;
&lt;P&gt;If your using ISE also to authenticate the device (802.1x) then you will need to keep ISE for the RADIUS authentication as I dont think intune can be a RADIUS server.&lt;/P&gt;
&lt;P&gt;If your more talking to do onboarding, then there are other solutions that dont need ISE&lt;/P&gt;</description>
      <pubDate>Thu, 23 Nov 2023 22:12:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965277#M263370</guid>
      <dc:creator>Haydn Andrews</dc:creator>
      <dc:date>2023-11-23T22:12:03Z</dc:date>
    </item>
    <item>
      <title>Re: WiFi profile</title>
      <link>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965281#M263373</link>
      <description>thank you for the reply&lt;BR /&gt;we are trying to onboard devices to Intune&lt;BR /&gt;</description>
      <pubDate>Thu, 23 Nov 2023 22:20:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965281#M263373</guid>
      <dc:creator>stephenstown20</dc:creator>
      <dc:date>2023-11-23T22:20:48Z</dc:date>
    </item>
    <item>
      <title>Re: WiFi profile</title>
      <link>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965406#M263385</link>
      <description>&lt;P&gt;The only way to bypass ISE authentication (or any other RADIUS server) by using EAP is to use EAP-GTC which is a Cisco proprietary EAP method. This EAP type requires a third-party supplicant on Windows devices, and it's available on MacOS using some MDM platforms like Apple's and JamF.&lt;/P&gt;
&lt;P&gt;But at the end, you need to use an Identitiy Manager like Azure AD or tradicional on-premise AD, but not Intune directly as this is only a MDM tool.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2023 07:21:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wifi-profile/m-p/4965406#M263385</guid>
      <dc:creator>JPavonM</dc:creator>
      <dc:date>2023-11-24T07:21:57Z</dc:date>
    </item>
  </channel>
</rss>

