Open mzv-itw opened 9 months ago
@mzv-itw Thanks for your feedback! We will investigate and update as appropriate.
@cwatson-cat Can you please check and add your comments on this doc update request as applicable.
@mzv-itw Thanks for bringing this to our attention. I'm going to assign this to the document author so they can take a look at it accordingly.
@prtanej Do you know if a new version of this connector is coming soon (that supports AMA): VMware vCenter connector for Microsoft Sentinel?
has there been any progress for support of Azure monitor agent with vCenter connector?the document still shows OMS agent the method of collection. Please advise. https://learn.microsoft.com/en-us/azure/sentinel/data-connectors/vmware-vcenter
Hello, any update on this ? The support for OMS will end soon
Curious if there is an update. I am doing this via the syslog ama and I am unsure if I would still need to use the conf file for the parser creation or not.
As of right now the solution still uses OMS/LAA agent and conf file. However I have heard that Microsoft are going to provide an updated solution, which uses AMA for vCenter logs before OMS goes end of life on the 31st of August. Suggest joining the Microsoft Security Connection program and joining the Teams channel where this is being discussed to get the latest. https://techcommunity.microsoft.com/t5/security-compliance-and-identity/the-new-microsoft-security-connection-program/ba-p/3733595
Hi,
Do these instructions also work for a log forwarder using the new Azure Monitor Agent (AMA)?
If not, can the article please be updated with those steps? We really don't want to set this up with the OMS agent since that is being retired in August 2024.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.