You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to integrate the Aruba Central platform for event monitoring into Microsoft Sentinel. Because there is no data connector for this solution, a case was escalated to Microsoft support. The information requested by Aruba Central to make the connection:
The Microsoft engineer conducted the investigation and the team's response was as follows:
“ _If the Aruba Central console requests a URL to send data, you must construct the URL as follows:
Index: This refers to the name of the type of record that will appear in log Analytics. You can use any descriptive name, for example, ArubaCentralEvents.
Token: Authentication is done using the Shared Key of the Log Analytics workspace._ "
Tests were made with the information sent by Microsoft but the result of the Aruba Central console shows that the destination is unreachable.
Due to issues beyond MS's control, the final customer took a long time to answer so MS closed the case, before reopening the case, I wanted to consult this blog to see if you can help me.
The text was updated successfully, but these errors were encountered:
Hello everyone.
I am trying to integrate the Aruba Central platform for event monitoring into Microsoft Sentinel. Because there is no data connector for this solution, a case was escalated to Microsoft support. The information requested by Aruba Central to make the connection:
The Microsoft engineer conducted the investigation and the team's response was as follows:
“ _If the Aruba Central console requests a URL to send data, you must construct the URL as follows:
Tests were made with the information sent by Microsoft but the result of the Aruba Central console shows that the destination is unreachable.
Due to issues beyond MS's control, the final customer took a long time to answer so MS closed the case, before reopening the case, I wanted to consult this blog to see if you can help me.
The text was updated successfully, but these errors were encountered: