Have you published the content to a publish environment?

I tried the Approach 2 mentioned above. However I ran into an issue which I wasn't able to get around. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/issue-with-adobe-target-powered-personalization-when-an-activity/qaq-p/359650#M73682

Here is the error I got in logsjava.lang.NullPointerException: nullat java.io.PrintWriter.write(Unknown Source)at com.adobe.granite.translation.connector.msft.core.impl.AccessTokenServlet.doPost(AccessTokenServlet.java:89) [com.adobe.granite.translation.connector.msft.core:1.3.24]at org.apache.sling...

As an alternative, install node and npm manually and run the following commands in the same order.In ui.frontendnpm installnpm run buildIn ui.appsmvn clean install -PautoInstallPackage.It will push both your Angular code as well as AEM code.

Just to rule out the DAM Update Asset workflow as the root cause of conflict. Can you disable the workflow and try if metadata update is happening ?

Yes this can be achieved. As a best practice, its better to put the configurations under project level /apps/<project-name>/config/ <your-configs-here>

Where are you adding additional classes ?

Since your requirement is site specific, you may need to write a custom login module and auth handler.

I am using AEM 6.5.0 on my local. I am trying to create translation configuration with microsoft as provider. I followed the following document:https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/tc-msconf.html  I am unable to successfully connect. When I enter t...

Seems like there was an error in the token that  used to make the API call. The token had expired. I created a new token and API is returning the response.