Cannot add validate or Azure SQL agent using Azure Active Directory in 7.3.0 (4377614)

Azure SQL database cannot be added or validated due to the following error after upgrading to 7.3.0.10.

ERROR [AGENTNAME-highPriorityPool-1] com.quest.qsi.fason.azure.collection.processor.DBSSAzureUsabilityResponseProcessor - Failed to get new connection on Usability-Response collection
com.quest.qsi.fason.core.errorhandling.AgentConnectionException: 'com.microsoft.aad.msal4j.AbstractClientApplicationBase$Builder com.microsoft.aad.msal4j.PublicClientApplication$Builder.executorService(java.util.concurrent.ExecutorService)'- Profile:AzureProfile{server='HOSTNAME', database= 'DATABASENAME', username='USERNAME', authType= 'AAD_PASSWORD', port= '1433', socketTimeout= '0', packetSize= '0', ApplicationIntent= 'NONE', enforceSSLVersion= 'NONE', lockTimeout= '10000', codePageOverride = '' }

"Caused by: java.lang.NoSuchMethodError: 'com.microsoft.aad.msal4j.AbstractClientApplicationBase$Builder com.microsoft.aad.msal4j.PublicClientApplication$Builder.executorService(java.util.concurrent.ExecutorService)'"

The issue is that version  1.15.0 of  msal4j removes the executorService method from AbstractClientApplicationBase#Builder and moves it to AbstractApplicationBase$Builder. This is fixed in later releases of msal4j. Replacing the 1.15.0 version with 1.17.2 resolves the issue.

WORKAROUND

Replace the current msal4j-1.15.0.jar file with a newer release

1. Deactivate the FglAM
2. Move msal4j-1.15.0.jar from {FglAM}\agents\DB_Azure_Database\{version}\lib folder to the desktop 
3. Copy the attached msal4j-1.17.2.jar file to the lib folder. The user must be logged into Supportlink to download this file.
4. Restart the FglAM and try to add the agent again
5. Generate new FglAM and FMS bundle it if does not work. We don't need all of the FglAM bundles this time, just the one used for this agent.

STATUS

This issue has been logged as defect FOG-10003 and will be fixed in an upcoming release of the Azure SQL cartridge.