Azure app service easy auth with Azure AD is not working for linux web app

Ravi Kumar Bomma [TechD] 1

Azure web app Easy auth (with Azure AD auth) is working for windows web apps, but not on Linux web app.
When I checked at web app logs, I could see that the container is failing to start when easy auth is enabled.

The Linux web app is working as is if I disable the easy-auth.
Technology stack of my web application: React SPA running on node LTS 14 environment on a azure Linux web app.

Not sure if I am missing something on configuration. Any help is appreciated.
Thanks in advance...

Update:
Today when I checked the container is starting successfully, which I can see from web app logs.
But the web page is not loading (showing 404).
But if I disable easy auth on web app the page loads as is.

Ryan Hill 25,981 Reputation points Microsoft Employee

2022-01-12T04:14:05.1+00:00

What's the error that you're getting @Ravi Kumar Bomma [TechD] ?
Ravi Chinni [TechD] 16 Reputation points

2022-01-12T11:30:33.09+00:00

Hi @Ryan Hill , its 404 web page not found on Linux Web App when Azure AD Authentication is enabled. Works fine if the Auth is diabled. And no issue on Windows Auth.
Ryan Hill 25,981 Reputation points Microsoft Employee

2022-01-12T19:41:10.05+00:00
@Ravi Chinni [TechD] , can you check the middleware logs by using one of the following methods and post any errors?

Under /home/LogFiles/xxxx-easyauth.docker.log.

Using Kudu https://sitename.scm.azurewebsites.net/api/logs/docker

Using Diagnose and solve problems blade > Application Logs detector.
Ravi Chinni [TechD] 16 Reputation points

2022-01-13T02:27:32.637+00:00

@Ravi Kumar Bomma [TechD] ,please see Ryan's latest reply and can you pull the logs.
Ravi Kumar Bomma [TechD] 1 Reputation point

2022-01-17T04:41:51.08+00:00

@Ryan Hill , please find the middleware logs I found.

----------
docker.log
INFO - Initiating warmup request to container webApp_1_a55bb9e8 for site webApp
INFO - Waiting for response to warmup request for container webApp_1_a55bb9e8. Elapsed time = 17.7604936 sec
INFO - Waiting for response to warmup request for container webApp_1_a55bb9e8. Elapsed time = 34.1128807 sec
INFO - Container webApp_1_a55bb9e8 for site webApp initialized successfully and is ready to serve requests.

---------easyauth_docker.log
This file is fully empty. No logs here.

----------
Ryan Hill 25,981 Reputation points Microsoft Employee

2022-01-21T23:59:59.86+00:00

Apologies for getting back to your so late @Ravi Kumar Bomma [TechD] . I started by following Tutorial: Sign in users and call the Microsoft Graph API from a React single-page app (SPA) using auth code flow and was successfully able to run it with an existing app registration. Afterwards, I added my app registration through the Authentication blade and began to experience issues where the app wasn't running. If you deploy a new app without a provider and instead use an existing app registration with MSAL, does your app run successfully?

In any case, we should work more closely with you to resolve your issue. Please follow the instructions in the private message below.
Ravi Kumar Bomma [TechD] 1 Reputation point

2022-01-22T07:35:34.893+00:00

@Ryan Hill , our app has Azure Ad auth with MSAL react, that is working fine. The problem starts when we enable it from authentication blade in Azure web app. Actually we need both authentications. These 2 are different ADs.