Merge pull request #229056 from Shereen-Bhar/activation-file-expiration

removing activation file expiration

Author: prmerger-automator[bot]

articles/defender-for-iot/organizations/how-to-activate-and-set-up-your-on-premises-management-console.md

@@ -70,8 +70,7 @@ After activating an on-premises management console, you'll need to apply new act
 |Location  |Activation process  |
 |---------|---------|
 |**On-premises management console**     |  Apply a new activation file on your on-premises management console if you've [modified the number of committed devices](how-to-manage-subscriptions.md#edit-a-plan-for-ot-networks) in your subscription.      |
-|**Cloud-connected sensors**     | Cloud-connected sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active. <br><br>If you're [updating an OT sensor from a legacy version](update-ot-software.md#update-legacy-ot-sensor-software), you'll need to re-activate your updated sensor.  |
-|  **Locally-managed**   |   Apply a new activation file to locally managed sensors every year. After a sensor's activation file has expired, the sensor will continue to monitor your network, but you'll see a warning message when signing in to the sensor.     |
+|**Cloud-connected and locally-managed sensors**     | Cloud-connected and locally-managed sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active. <br><br>If you're [updating an OT sensor from a legacy version](update-ot-software.md#update-legacy-ot-sensor-software), you'll need to re-activate your updated sensor.  |
 
 For more information, see [Manage Defender for IoT subscriptions](how-to-manage-subscriptions.md).
 

articles/defender-for-iot/organizations/how-to-activate-and-set-up-your-sensor.md

@@ -131,16 +131,12 @@ For information about uploading a new certificate, supported certificate paramet
 
 ### Activation expirations
 
-After activating a sensor, you'll need to apply new activation files as follows:
+After activating a sensor, cloud-connected and locally-managed sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active.
 
-|Location  |Activation process  |
-|---------|---------|
-|**Cloud-connected sensors**     | Cloud-connected sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active. <br><br>If you're [updating an OT sensor from a legacy version](update-ot-software.md#update-legacy-ot-sensor-software), you'll need to re-activate your updated sensor.   |
-|  **Locally managed**   |   Apply a new activation file to locally managed sensors every year. After a sensor's activation file has expired, the sensor will continue to monitor your network, but you'll see a warning message when signing in to the sensor.     |
+If you're updating an OT sensor from a legacy version, you'll need to re-activate your updated sensor. For more information, see [Update legacy OT sensor software](update-ot-software.md#update-legacy-ot-sensor-software).
 
 For more information, see [Manage Defender for IoT subscriptions](how-to-manage-subscriptions.md) and [Manage the on-premises management console](how-to-manage-the-on-premises-management-console.md).
 
-
 ### Activate an expired license (versions under 10.0)
 
 For users with versions prior to 10.0, your license may expire, and the following alert will be displayed.
@@ -283,6 +279,6 @@ For more information, see:
 
 - [Onboard a sensor](tutorial-onboarding.md#onboard-and-activate-the-virtual-sensor)
 
-- [Manage sensor activation files](how-to-manage-individual-sensors.md#manage-sensor-activation-files)
+- [Manage sensor activation files](how-to-manage-individual-sensors.md#upload-a-new-activation-file)
 
 - [Control what traffic is monitored](how-to-control-what-traffic-is-monitored.md)

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

@@ -63,70 +63,39 @@ In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defe
 
 For more information, see [Update Defender for IoT OT monitoring software](update-ot-software.md).
 
-## Manage sensor activation files
+## Upload a new activation file
 
-Your sensor was onboarded with Microsoft Defender for IoT from the Azure portal. Each sensor was onboarded as either a locally connected sensor or a cloud-connected sensor.
+Each OT sensor is onboarded as a cloud-connected or locally-managed OT sensor and activated using a unique activation file. For cloud-connected sensors, the activation file is used to ensure the connection between the sensor and Azure.
 
-A unique activation file is uploaded to each sensor that you deploy. For more information about when and how to use a new file, see [Upload new activation files](#upload-new-activation-files). If you can't upload the file, see [Troubleshoot activation file upload](#troubleshoot-activation-file-upload).
-
-### About activation files for locally connected sensors
-
-Locally connected sensors are associated with an Azure subscription. The activation file for your locally connected sensors contains an expiration date. One month before this date, a warning message appears in the System Messages window in the top-right corner of the console. The warning remains until after you've updated the activation file.
-
-You can continue to work with Defender for IoT features even if the activation file has expired.
-You can continue to work with Defender for IoT features even if the activation file has expired.
-
-### About activation files for cloud-connected sensors
-
-Sensors that are cloud connected aren't limited by time periods for their activation file. The activation file for cloud-connected sensors is used to ensure the connection to Defender for IoT.
-
-### Upload new activation files
-
-You might need to upload a new activation file for an onboarded sensor when:
-
-- An activation file expires on a locally connected sensor.
-
-- You want to work in a different sensor management mode.
-
-- For sensors connected via an IoT Hub ([legacy](architecture-connections.md)), you want to assign a new Defender for IoT hub to a cloud-connected sensor.
+You'll need to upload a new activation file to your senor if you want to switch sensor management modes, such as moving from a locally-managed sensor to a cloud-connected sensor. Uploading a new activation file to your sensor includes deleting your sensor from the Azure portal and onboarding it again.
 
 **To add a new activation file:**
 
-1. Go to the Azure portal for Defender for IoT.
-1. Use the search bar to find the sensor you need.  
+1. In [Defender for IoT on the Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started) > **Sites and sensors**, locate and [delete](how-to-manage-sensors-on-the-cloud.md#sensor-maintenance-and-troubleshooting) your OT sensor.
 
-1. Select the three dots (...) on the row and select **Delete sensor**.
+1. Select **Onboard OT sensor > OT** to onboard the sensor again from scratch. For more information, see [Onboard OT sensors](onboard-sensors.md)
 
-1. Onboard the sensor again by selecting **Getting Started**>  **Set up OT/ICS Security** > **Register this sensor with Microsoft Defender for IoT**.
+1. On the **sites and sensors** page locate the sensor you just added. 
 
-1. Go to the **Sites and sensors** page.
-
-1. Use the search bar to find the sensor you just added, and select it.
-1. Select the three dots (...) on the row and select **Download activation file**.
+1. Select the three dots (...) on the sensor's row and select **Download activation file**. Save the file in a location accessible to your sensor.
 
     [!INCLUDE [root-of-trust](includes/root-of-trust.md)]
 
-1. Save the file.
-
-1. Sign in to the Defender for IoT sensor console.
-
-1. Select **System Settings** > **Sensor management** > **Subscription & Activation Mode**.
+1. Sign in to the Defender for IoT sensor console and select **System Settings** > **Sensor management** > **Subscription & Activation Mode**.
 
-1. Select **Upload** and select the file that you saved.
+1. Select **Upload** and browse to the file that you downloaded from the Azure portal.
 
-1. Select **Activate**.
+1. Select **Activate** to upload your new activation file.
 
 ### Troubleshoot activation file upload
 
 You'll receive an error message if the activation file couldn't be uploaded. The following events might have occurred:
 
-- **For locally connected sensors**: The activation file isn't valid. If the file isn't valid, go to [Defender for IoT in the Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started). On the **Sensor Management** page, select the sensor with the invalid file, and download a new activation file.
-
-- **For cloud-connected sensors**: The sensor can't connect to the internet. Check the sensor's network configuration. If your sensor needs to connect through a web proxy to access the internet, verify that your proxy server is configured correctly on the **Sensor Network Configuration** screen. Verify that the required endpoints are allowed in the firewall and/or proxy.
+- **The sensor can't connect to the internet:** Check the sensor's network configuration. If your sensor needs to connect through a web proxy to access the internet, verify that your proxy server is configured correctly on the **Sensor Network Configuration** screen. Verify that the required endpoints are allowed in the firewall and/or proxy.
 
     For OT sensors version 22.x, download the list of required endpoints from the  **Sites and sensors** page on the Azure portal. Select an OT sensor with a supported software version, or a site with one or more supported sensors. And then select **More actions** > **Download endpoint details**. For sensors with earlier versions, see [Sensor access to Azure portal](how-to-set-up-your-network.md#sensor-access-to-azure-portal).
 
-- **For cloud-connected sensors**: The activation file is valid but Defender for IoT rejected it. If you can't resolve this problem, you can download another activation from the **Sites and Sensors** page in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started). If this doesn't work, contact Microsoft Support.
+- **The activation file is valid but Defender for IoT rejected it:** If you can't resolve this problem, you can download another activation from the **Sites and Sensors** page in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started). If this doesn't work, contact Microsoft Support.
 
 ## Manage certificates
 

articles/defender-for-iot/organizations/how-to-manage-sensors-on-the-cloud.md

@@ -119,7 +119,7 @@ In such cases, do the following steps:
 
 1. [Delete your existing sensor](#sensor-management-options-from-the-azure-portal).
 1. [Onboard the sensor again](onboard-sensors.md#onboard-an-ot-sensor), registering it with any new settings.
-1. [Upload your new activation file](how-to-manage-individual-sensors.md#upload-new-activation-files).
+1. [Upload your new activation file](how-to-manage-individual-sensors.md#upload-a-new-activation-file).
 
 ### Reactivate an OT sensor for upgrades to version 22.x from a legacy version
 

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

@@ -150,7 +150,7 @@ Billing changes will take effect one hour after cancellation of the previous sub
 
     - For sensors monitoring overlapping network segments, create the activation file under the same zone. Identical devices that are detected in more than one sensor in a zone, will be merged into one device.
 
-1. [Upload a new activation file](how-to-manage-individual-sensors.md#upload-new-activation-files) for your sensors under the new subscription.
+1. [Upload a new activation file](how-to-manage-individual-sensors.md#upload-a-new-activation-file) for your sensors under the new subscription.
 
 1. Delete the sensor identities from the previous subscription. For more information, see [Sensor management options from the Azure portal](how-to-manage-sensors-on-the-cloud.md#sensor-management-options-from-the-azure-portal).