I've been setting up Github Advanced Security for Azure Devops, to use with Git hosted in Azure Devops (not Github), which has been largely successful. For the secret scanning, the system has identified existing secretes in our solutions, and I've enabled secret blocking on pushes which is also working well. However on the Security Overview page, Alerts for Secrets shows as disabled (see below), which suggests that there is a capability that has not been enabled.
What actions need to be undertaken to enable alerts for Secrets?
You can run REST API Repo Enablement - Get to check the enablement of your target repo.
For data retrieval on the security overview dashboard, it is using REST API Org Enablement - Get to gather summaries of enablement and alerts data. It may take some time for the backend job to gather the necessary data for the dashboard. Sometimes there may be some problems. Therefore, the security overview may be delayed or inconsistent with the actual situation.
Typically, if you have enabled Advanced Security for your repository, secret scanning is enabled.
It is recommended that you refer to the actual result. You can try to push a secret to your repository and see if it is discovered.