<?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>question Re: Microsoft Intune Spoke VS Service Graph Connector for Microsoft Intune in CMDB forum</title>
    <link>https://www.servicenow.com/community/cmdb-forum/microsoft-intune-spoke-vs-service-graph-connector-for-microsoft/m-p/3245764#M15368</link>
    <description>&lt;P&gt;From my experience you wont nessisarrly need the spoke if you use the service graph connector. The service Graph connector imports large amounts of Intune data into the ServiceNow CMDB while the spoke can be used for in IntegrationHub to do individual things like "Get managed Applications", "Look up managed Applications", "Update Managed Devices"... things like that. You would build a flow with the spoke to do differnt actions while the service graph securely manages all of your devices with a single endpoint solution. Hope this helps.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Apr 2025 17:37:45 GMT</pubDate>
    <dc:creator>frank121</dc:creator>
    <dc:date>2025-04-23T17:37:45Z</dc:date>
    <item>
      <title>Microsoft Intune Spoke VS Service Graph Connector for Microsoft Intune</title>
      <link>https://www.servicenow.com/community/cmdb-forum/microsoft-intune-spoke-vs-service-graph-connector-for-microsoft/m-p/2734440#M7753</link>
      <description>&lt;P&gt;Hello!&lt;BR /&gt;We need to&amp;nbsp;migrate to Intune from SCCM and&lt;/P&gt;&lt;P&gt;intall the plugin for&amp;nbsp;Service Graph Connector for Microsoft Intune.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do we need to also install&amp;nbsp;Microsoft Intune Spoke plugin?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the difference between them?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 16 Nov 2023 10:20:35 GMT</pubDate>
      <guid>https://www.servicenow.com/community/cmdb-forum/microsoft-intune-spoke-vs-service-graph-connector-for-microsoft/m-p/2734440#M7753</guid>
      <dc:creator>angelicaodnc</dc:creator>
      <dc:date>2023-11-16T10:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Intune Spoke VS Service Graph Connector for Microsoft Intune</title>
      <link>https://www.servicenow.com/community/cmdb-forum/microsoft-intune-spoke-vs-service-graph-connector-for-microsoft/m-p/3210405#M14919</link>
      <description>&lt;P&gt;Anyone please comment.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 15:18:46 GMT</pubDate>
      <guid>https://www.servicenow.com/community/cmdb-forum/microsoft-intune-spoke-vs-service-graph-connector-for-microsoft/m-p/3210405#M14919</guid>
      <dc:creator>poojatanwar</dc:creator>
      <dc:date>2025-03-18T15:18:46Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Intune Spoke VS Service Graph Connector for Microsoft Intune</title>
      <link>https://www.servicenow.com/community/cmdb-forum/microsoft-intune-spoke-vs-service-graph-connector-for-microsoft/m-p/3245764#M15368</link>
      <description>&lt;P&gt;From my experience you wont nessisarrly need the spoke if you use the service graph connector. The service Graph connector imports large amounts of Intune data into the ServiceNow CMDB while the spoke can be used for in IntegrationHub to do individual things like "Get managed Applications", "Look up managed Applications", "Update Managed Devices"... things like that. You would build a flow with the spoke to do differnt actions while the service graph securely manages all of your devices with a single endpoint solution. Hope this helps.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Apr 2025 17:37:45 GMT</pubDate>
      <guid>https://www.servicenow.com/community/cmdb-forum/microsoft-intune-spoke-vs-service-graph-connector-for-microsoft/m-p/3245764#M15368</guid>
      <dc:creator>frank121</dc:creator>
      <dc:date>2025-04-23T17:37:45Z</dc:date>
    </item>
  </channel>
</rss>

