Deploying to Azure doesnt behave as gatsbycloud does.

[shobz]

Hi everyone.
I hope everyone is safe. I was deploying the gatsby on Azure Static website and also on Azure App services.
Following the link https://www.gatsbyjs.com/docs/how-to/previews-deploys-hosting/deploying-to-azure/

I did the steps and it worked I can see the main page but when I go to other links it doesnt work, but on the demo url by gatsby it works...

Here is official gatsby demo link https://gatsbystarterdefaultsource.gatsbyjs.io/
and go to this page https://gatsbystarterdefaultsource.gatsbyjs.io/using-ssr hit refresh
They work fine..

Now Azure Static webapp deployment URL
https://purple-grass-00935d410.azurestaticapps.net/

You can view the pages for example Typescript and main page and hit refresh and everything is cool. Try yourself try to deploy gatsby on azure static web app and see you can not navigate to using-ssr page.
Then I got a config file for routes which I added and re-deployed and now using-ssr and using-dsg takes me to index/root...
here is staticwebapp.config.json file

{ "navigationFallback": { "rewrite": "index.html", "exclude": ["*.{png,jpg,gif,svg,ico}", "*.css"] } }

Gatsby on Azure App Service - Linux container and also on windows container
I created a Project on .NET Core MVC and added webapp folder did all the requirements and successfully deployed the gatsby build on it. There are two problems there :) On windows container you have to insert a file web.config and I did it worked but same issues :) it will take you to root/index file. If you have two pages index.js and about.js and linked them using GATSBY LINK it will work if you press the links but when you hit the refresh it will take you to root. I re-deployed on linux container it worked but same thing there.

Solutions I get are for NEXTJS where everyone suggest a server.js and webconfig file and instructions. I can not see anything related to gatsby. I am trying to deploy gatsby's official starter on app services -- trying again....

It would be great if some has successfully deployed and overcame this issue.

Thanks.