search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.27k stars 21.45k forks source link

Onboarding EIoT sensors is no longer accurate. #117829

Closed wompRS closed 6 months ago

wompRS commented 10 months ago

The section: https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/eiot-sensor#register-an-enterprise-iot-sensor-in-defender-for-iot

This section states that you must go to sites and sensors, click on onboard, and choose EIoT to onboard the EIoT sensor. This button is supposed to be there and then pop up a page that gives you the EIoT registration details (command).

This is no longer showing up in any of our organization's azure menus. We tried this about a month ago and it worked, but the button no longer exists in a dropdown format and only brings you to the OT sensor registration, not EIoT sensor.

image

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

RamanathanChinnappan-MSFT commented 10 months ago

@wompieRS I've delegated this to @batamig, a content author, to review and share their valuable insights.

wompRS commented 10 months ago

Can I have an update on this? This is pretty critical. People are not able to onboard Enterprise IOT sensors as it stands.

batamig commented 10 months ago

Hi @wompieRS, thanks for writing into docs! I'm tagging @amitcohen25 as a subject matter expert on the Enterprise IoT sensor. We'll then be updating the documentation as needed to clarify.

amitcohen25 commented 10 months ago

Hi @wompieRS, the enterprise IoT sensor's availability was updated when Enterprise IoT was included in the E5 package ( https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/whats-new#enterprise-iot-protection-now-included-in-microsoft-365-e5-and-e5-security-licenses), making it accessible only to ACR-based customers. That's why you enterprise IoT sensor is not available for new customers. We will make sure to update the documentation.

Please note that Microsoft Defender for Endpoint's device discovery continue be the main discovery source for enterprise IoT devices connected to an IT network (for example, Voice over Internet Protocol (VoIP), printers, and smart TVs). More details available here: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/device-discovery?view=o365-worldwide

wompRS commented 10 months ago

While that may be the case for new customers, I am an E5 customer and have been for several years. This is happening on the tenant that I hold an E5 license to. I am not a new customer.

On Wednesday, Dec 20, 2023, 4:09 AM, wrote:

Hi @wompieRS, the enterprise IoT sensor's availability was updated when Enterprise IoT was included in the E5 package ( https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/whats-new#enterprise-iot-protection-now-included-in-microsoft-365-e5-and-e5-security-licenses), making it accessible only to ACR-based customers. That's why you enterprise IoT sensor is not available for new customers. We will make sure to update the documentation. Please note that Microsoft Defender for Endpoint's device discovery continue be the main discovery source for enterprise IoT devices connected to an IT network (for example, Voice over Internet Protocol (VoIP), printers, and smart TVs). More details available here: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/device-discovery?view=o365-worldwide You are receiving this because you were mentioned.Message ID:

batamig commented 6 months ago

reassign:limwainstein

limwainstein commented 6 months ago

We've updated the documentation to state that registering a new Enterprise IoT network sensor is no longer available. For customers with the Azure Consumption Revenue (ACR) or legacy license, Defender for IoT maintains existing Enterprise IoT network sensors. See: https://learn.microsoft.com/en-us/azure/defender-for-iot/organizations/eiot-sensor

limwainstein commented 6 months ago

I'm closing the issue, but please let us know if you have any additional questions. @wompRS

limwainstein commented 6 months ago

please-close