Make Discovery Status Visible After Updating Credentials for Azure

While updating credentials (App registration details/Client secret value) for our Azure tenant, we are unable to manually rediscover Azure targets. At least, that's what it appears to be happening when you attempt to click on the ellipses next to the subscription and select Rediscover.  If you attempt to rediscover the child Azure subscriptions, it just says it fails and the details shows an older timestamp when the system last discovered it automatically. Apparently from support, this is "designed" behavior and that it's just using cached data from the last discover attempt. Why would this be using cached data for an action I request immediately? Upon updating the secret value for the Azure Service Principal target, it'll complete that part successfully. The UI won't show any of the child Azure subscription targets in a "Discovering" state after that change but rather in the Critical state still. Support also indicated that a discovery could in fact be running in the background or queued, but the UI just shows each of the Azure subscriptions in a critical state due to a failed discovery. After a few minutes of showing a critical state, the subscription will show a normal status after doing a refresh. No indication at all that a discovery took place.
 

What should happen is the UI should report that the subscriptions are in fact in a discovery state as any normal routine discovery does. This would show the user that the update to the credentials in the app registration details was successful and show a more real time status. Otherwise, it makes it look like you entered a wrong secret value because it still remains in a failed, critical state.

You can easily replicate this behavior by putting in a wrong secret value, rediscover and make sure the subscriptions are in a critical state. Then put back the correct secret value and you'll observe that nothing happens when you click the rediscover link and there's no indication of the subs being rediscovered otherwise.

I think this is more of a bug fix than a feature request as I don't believe this is intended or "designed" functionality.