reedit

tarTech23 · tarTech23 · commit bd0f4e0c4971 · 2024-09-18T16:37:41.000+03:00
diff --git a/defender-for-iot/includes/site-association.md b/defender-for-iot/includes/site-association.md
@@ -8,7 +8,5 @@ ms.service: microsoft-defender-iot
 
 >[!NOTE]
 >
->In the Defender XDR portal, devices are discovered using Microsoft Defender for Endpoint and associated with sites created in Site Security. Whereas in Azure devices are discovered using the Defender for IoT network sensors and then associated with a site.
->
->Currently, sites created in the different portals aren't synchronized yet and therefore the list of devices discovered by Azure and the Defender XDR portal could be different.<!-- (We plan to enable the association of devices discovered by both MDE and Network Sensors in the Defender XDR portal in the near future.) - Limor do we also want to add this, Amit wasnt sure> -->
+>Currently, devices discovered in the Defender XDR portal aren't synchronized with Azure, and therefore the list of devices discovered could be different in each portal. It is important to note these differences, especially when associating devices to a site. This issue will be resolved in upcoming versions.
 >

Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,5 @@ ms.service: microsoft-defender-iot`
`8`	`8`
`9`	`9`	`>[!NOTE]`
`10`	`10`	`>`
`11`		`->In the Defender XDR portal, devices are discovered using Microsoft Defender for Endpoint and associated with sites created in Site Security. Whereas in Azure devices are discovered using the Defender for IoT network sensors and then associated with a site.`
`12`		`->`
`13`		`->Currently, sites created in the different portals aren't synchronized yet and therefore the list of devices discovered by Azure and the Defender XDR portal could be different.<!-- (We plan to enable the association of devices discovered by both MDE and Network Sensors in the Defender XDR portal in the near future.) - Limor do we also want to add this, Amit wasnt sure> -->`
	`11`	`+>Currently, devices discovered in the Defender XDR portal aren't synchronized with Azure, and therefore the list of devices discovered could be different in each portal. It is important to note these differences, especially when associating devices to a site. This issue will be resolved in upcoming versions.`
`14`	`12`	`>`