124 votes22 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →
Hi folks! I apologies for the delay in response and I deeply appreciate your feedback. I understand how important this feature is for your and your users. We do not yet have plans to implement this feature, but please keep voting if this is important to you to help us prioritize appropriately.
332 votes20 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
This is currently under development, scheduled to be in preview later in 2018Rodrigo commented
There are plenty of information that can only be retrieved from a workstation's event logs. Think about AppBlocker, EMET and other security-related events that are currently only logged into a local event log. Until a properly priced SKU for non-server nodes exists, having the ability to forward events from a workstation to a central repository and funnel that up to OMS is the only way to get that that data into one pane for the folks checking those things. Granted you can technically write your own solution to parse those local logs, package the entries into JSON and ingest them into OMS via the HTTP API but it would be nicer if we had some pre-canned option.
We continue to investigate this. Due to the current roadmap and strategy this will remain in our backlog. Please continue to share feedback related to this topic to help us make an informed decision at a later time.
3 votes4 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →Rodrigo commented
Have you tried manually typing "AD FS/Admin" (without quotes) as the event log name and clicking the add button (+)? We did that on our implementation and started collecting logs from our ADFS Servers.