Skip to content

Commit 9fca045

Browse files
authored
Merge pull request #208118 from yoninalmsft/patch-6
add privacy notice deleting data in MDE
2 parents 8c87906 + 511e168 commit 9fca045

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/defender-for-iot/organizations/how-to-manage-subscriptions.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,9 @@ Delete all sensors that are associated with the subscription prior to removing t
159159
> [!NOTE]
160160
> To remove Enterprise IoT only from your plan, cancel your plan from Microsoft Defender for Endpoint. For more information, see the [Defender for Endpoint documentation](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration#cancel-your-defender-for-iot-plan).
161161
162+
> [!IMPORTANT]
163+
> If you are a Microsoft Defender for IoT customer and also have a subscription to Microsoft Defender for Endpoint, the data collected by Microsoft Defender for IoT will automatically populate in your Microsoft Defender for Endpoint instance as well. Customers who want to delete their data from Defender for IoT must also delete their data from Defender for Endpoint.
164+
162165
## Move existing sensors to a different subscription
163166

164167
Business considerations may require that you apply your existing IoT sensors to a different subscription than the one you’re currently using. To do this, you'll need to onboard a new plan and register the sensors under the new subscription, and then remove them from the old subscription. This process may include some downtime, and historic data isn't migrated.

0 commit comments

Comments
 (0)