Working through deploying to azure webapps, wish me luck, I’ll update this thread with progress. Currently on a call with azure help refining the docker build. 
1 Like
Hows it going?
Ugh not great, I’m the frontend dev at a startup and I reached for Redwood because I’ve had a breeze deploying to Netlify and AWS, and * the docs mention out of the box config for Azure *
*This was a mistake on my end, the docs do not mention out of the box config for deployment. but I didn’t run a hello world build prior to putting work into it and I’m not great at devops so my amazing dev team have been working on workarounds with Azure helpdesk and I’m out of my depth of knowledge. We keep knocking down errors but running into new ones, currently we have a local dockerfile building successfully but it breaks on deployment to Azure webapps.
I don’t want to abandon Redwood because I love it, but I’m also out of my depth of knowledge on the dev ops side of things. Any help or reference to the docs would be greatly appreciated, it would make me so happy to be able to solve deploying our app to Azure and contribute the solution to this wonderful community! 
Hi. I’m not sure that the docs offer out of the box deployment to Azure - but rather an option to use Azure Active Directory as authentication provider.
There are two parts to any deployment - an api side where the requests are based on Lambas (hence why Netlify deploy works well and Vercel as they transform the lamba event to what they need) and the web react spa deploy which is typically done on some CDN. And then tells two sides need to talk to each other.
The Azure part isn’t supported as the function event lambda is a bit different.
Alternatively deploys via Docker in a serverful way may be an option say on Fly.
Is there a specific business need to deploy on Azure over other options?
I edited my post, for clarity but left it up so as not to confuse others.
You’re absolutely right, I must have misread the docs referencing AD.
Our business need is that we already have a lot of our backend built out on Azure, I’m trying to make the case for lift/shifting to AWS serverless, the counter option proposed is Nextjs. I would like to be up front about the fact that I’m basically a Junior dev who got handed an opportunity to choose the frontend and I’m now wildly outside my wheelhouse, if there’s a solid way to use redwood deployed outside of Azure and connect it to Azure endpoints or other options I’m super open to suggestions, but as of right now the business side of things is putting the pressure on and I either need to find a solution with Redwood or move on.
Thanks again Barrett and David, this one’s on me and I appreciate you guys!
Out of curiosity how do you propose deploying NextjS to Azure?
I ask because of this post by the founder of Netlify saying that it’s the only place besides Vercel where next can be deployed in a serverless way: x.com
And wow the amount of code to make that happen GitHub - opennextjs/opennextjs-netlify: Open Next.js adapter for Netlify
1 Like
Is your existing azure api graphql? Did you plan to rewrite the api as graphql?
We have been running an RW application on Azure for months now. It is definitely not an out-of-the-box solution, but we are happy with our system. My colleague tried to share the important parts in this post:
1 Like
We have been running our RW application on Azure for 1½ years now and are satisfied with it too. We run a docker container for the backend in Azure Web App (inspired by the original post by @tomdickson that you referenced).
As for the frontend, we have a similar setup to this: Deploy to Azure Static Web Apps
1 Like
Such helpful insights David, thank you so much for saving us from a headache!
We currently have resources in Azure that will tie into our graphql endpoint (blob, db, etc.).
Good news all, we got the web side deployed and are now working through the api side!!
Huge thanks to Tillmannb for the solution, we were able to use the github action you provided, and once we get the api deployed I’ll share our final working solution.
You are all been so helpful, I can’t thank you enough!