Azure Active Directory
Welcome to the Azure Active Directory suggestions and feedback site! We love hearing from you. If you have suggestions, please submit an idea or vote up an idea. We are monitoring the site actively.
Thank you for joining our community and helping improve Azure AD!
Wehave a new log in experience integrated with Azure AD, and we stronglyrecommend you log in with your Azure AD (Office 365) account. If yourUserVoice account is the same email address as your Azure AD account, yourprevious activities will be automatically mapped to your Azure AD account. You can read more here for details: https://techcommunity.microsoft.com/t5/Azure-Active-Directory-Identity/Putting-customers-first-for-f...
-
Add report for Extranet Lockout Protection - Account Lockout
Add a new report to Azure AD Connect Health that allows support staff to see which accounts are locked out by ADFS Extranet Lockout Protection.
43 votes -
Integrate Azure AD Connect Health with OMS/Log Analytics
This information should be available in OMS/Log Analytics, as a one stop shop for all monitoring... It should not be available only separately to OMS/Log Analytics!
40 votesThanks for the feedback. Connect Health team is planning to integrate Connect Health data with Log Analytics in phases. The first stream of ADFS data will be available in 3-6 months for preview.
Please reach out to askaadconnecthealth at microsoft.com for preview request. -
SCOM Management Pack for Azure AD Connect
Please create a management pack for SCOM to monitor AAD Connect, including the Pass-through authentication functionality. This is a critical component in the Microsoft cloud ecosystem. All on-prem products are supposed to be shipped with a SCOM management pack for monitoring them. This has been in prod for years and it is still missing.
And no, AD Connect health does not cut it. For example, it does not even send an alert email when the "Microsoft AAD Application Proxy Connector" is not running.
30 votesThank you for the feedback. This is under review. We will in touch with SCOM team to assess this request.
-
I would love to be able to export and search the ADFS bad password attempts!
I would love to be able to export and search the ADFS bad password attempts!
18 votesThank you for the feedback! Azure AD Connect Health team is planning to provide a solution of this report. We will update in this thread further once it is ready for preview.
-
Include an AAD Connect Health Gateway for DCs without internet connectivity
An easy to configure gateway install similar to the OMS gateway to act as a proxy for servers without internet connectivity would be a useful addition.
15 votesThank you Jeremy for the great feedback.
We started to review the work of adding the proxy to health agent in our ADDS agent. -
Azure AD Connect Health Bad Password Report improvement
Add which application was the bad password logged against.
15 votesThank you for the feedback! Azure AD Connect Health team is planning to provide a solution of this report. We will update in this thread further once it is ready for preview
-
AD Connect Sync stopped-deletion-threshold-exceeded: Allow to get an export list (CSV or Excel file) of all objects marked for deletion
Allow the possibility to export the list of users that appear in threshold so they can be verified before disabling it.
As you know, if you want to delete more than 500 objects in local AD, AD Connect won;t allow you to do this. We need a way to export those users just to make sure that they are not removed by mistake.
Thank you!
10 votesThank you for the feedback! Azure AD Connect Health team is planning to provide a solution of this report. We will update in this thread further once it is ready for preview
-
Test Authentication Request (Synthetic Transaction) failed to obtain a token.
Hi Team,
I am receiving ADFS alerts as mentioned in the subject, but while I test the ADFS Server health, the test is getting passed. But I offen get this alert, can some one help me in fixing this.
thanks in advance.
Regards,
Naveen Ramakrishnan10 votesUpdate the status
-
Integrate Azure AD Connect Health ADFS Failed Logins and Lockout Events with Microsoft Cloud App Security
The ADFS auditing events for logon failures or account lockout collected by the Azure AD Connect Health agent for ADFS on all the on-premise ADFS servers are not shared with the central Azure Security solutions such as:
1. Azure AD Identity Protection
2. Office365 Cloud App Security (OCAS)
3. Microsoft Cloud App Security (MCAS).There is no available method to integrate or correlate these events with the rest of the Azure security solutions. The result is that this limit heavily the brute force attacks detection on the ADFS infrastructure. The only available option is to collect the logs locally through…
7 votesThank you for your feedback.
We are planning to work with Azure Identity Protection team to have enhanced security features for ADFS. -
Show AADConnect version when upgrading
Show the AADConnect Version you are upgrading to when starting the Wizard and once complete, show the version again.
6 votes -
AD Connect Health ADDS Agent should not require WOW64
We have been removing WOW64 Support from all Server Core installs. Not happy about adding it back on DCs for an agent.
6 votes -
Support other notification types for Azure AD Connect Health
Add other options for notifications other than e-mail. Webhook would be especially useful, or ITSM connector. If it reported to Log Analytics, these would be available.
5 votes -
Alert on 80% and 90% usage for SQL Server 2012 Express LocalDB with 10GB size limit
Please add some monitoring for the database size for Azure AD Connect with a SQL Server 2012 Express LocalDB (10GB size limit).
Customers needs to be made aware before they hit the limit. Send alerts when customer hit 8-9GB usage on the DB.
5 votesThank you Peter for the feedback! Azure AD Connect Health team is working on this alert and should be available very soon.
-
Azure AD Connect Sync Tool - Allow sync by selecting specific AD Groups - Not by OU
We are using the Azure AD Connect sync tool and would like to be able to synchronize a selection of on premise AD security groups. This would allow us the ability to create a set of Azure groups on premise that we add users to and specifically grant access to our azure AD. Then in Azure we can set those permissions to azure resources as needed. This allows us to add and remove users on prem easily and synchronize ONLY those users we want to have access to Azure. This keeps our Azure AD clean and relevant. The current tool…
4 votes -
AADC Health - Notification when AADC Scheduler is disabled
Send a notification when AADC Scheduler is disabled or when sync didn't happen for x number of hours/days.
4 votesThanks for the feedback!
This is in our backlog and our engineers are working on the new alert. -
Azure AD exposing user info in new portal
Azure AD in the new portal exposes the Users and groups listed in the AD. This was data that was not accessible to users in the AD while still on the old portal. Now normal users can view all details in the AD. Is this meant to be so in the new portal? If Yes, is there a way to disable this for normal users via the portal or from the backend by submitting a request?
4 votes -
Provide the ability to configure notification alerts within the Health App
Configure e-mail alerts on messages from the “Azure Active Directory Connect (Sync) Alerts”. Currently only errors are alerted and unable to configure to warning messages.
4 votesThank you for the feedback! We will review the experience and enhance the notification feature.
-
Azure AD Connect Health Pass-through Authentication Agent Support
Please add support for monitoring the Azure AD Pass-through Authentication Agent to Azure AD Connect Health. This is current a gap in that when you use Pass-through Authentication (PTA) the agents are not monitored and there is no way to do this via Azure AD Connect Health currently. The PTA agent is a critical service when using Pass-Through Authentication so this should be monitored.
3 votes -
Azure AD Connect Health Agent for ADDS should use the OMS agent
Rather than requiring a separate agent install, leveraging the Microsoft Monitoring Agent would be appetizing to customers looking to minimize their agent footprint on DCs.
3 votes -
"Required SSL bindings are missing or not configured. " alert from AD Health Connect includes steps for Server 2012 but not for 2016.
Provide steps to correct for 2016 servers
3 votes
- Don't see your idea?