deploy to azure button with Bicep files.

[skmkzyk]

The "deploy to Azure" button doesn't accept Bicep files currently.
What is the workaround for this situation for now?

I think the below way but got CORS error on Azure Portal.

1. Execute "bicep build" by GitHub actions and get release URL ("https://github.com/foo/bar/releases/latest/download/azuredeploy.json").
2. Create a "deploy to Azure" button link with this URL. ([![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fgithub.com%2Ffoo%2Fbar%2Freleases%2Flatest%2Fdownload%2Fazuredeploy.json))

[brwilkinson]

Adding @bmoore-msft to note your expression of interest for this.

The current recommendation with all quickstarts is to have your Bicep Templates with modules, however also include the main.json file which is the compiled ARM template version of your Bicep files.

So in that case you just have to do the extra step to build your Bicep and then still use the json for the deploy to Azure.

[tsubasaxZZZ]

He is talking about JSON file that after built from Bicep by GitHub Actions. It's located on Release page at GitHub and use "latest" URL.

For example:

Above URL indicates following JSON that is latest Release asset:
https://github.com/azure/reliability-workbook/releases/latest/download/azuredeploy.json

[brwilkinson]

@tsubasaxZZZ just to confirm... @skmkzyk wants to be able to have a Deploy to Azure button, by using a Bicep file. Which saves the extra step of building it to the json ARM Template file.

This is not currently supported and is not planned, since the Portal doesn't currently accept Bicep Files for deployments. However, given this likely a common ask and will grow in popularity as more people move to Bicep.

We should track the item as backlog, so hopefully @bmoore-msft has some idea on priority and see if there was any current plan for this.

[brwilkinson]

just to add, when I said:

"however also include the main.json"

I had actually meant to say:

"however also include the azuredeploy.json"

[skmkzyk]

You're correct. Sorry for my little mistake ><

[bmoore-msft]

I don't think we have an ETA for allowing the portal to accept the bicep file directly... (it's on the list, but no date yet).

From the error is looks like the CORS settings on github release artifacts are too strict for the Portal (I'm not a CORS expert by any means). I couldn't find anyway to configure that in a repo but the github folks may know more... The Portal has the correct behavior.

In the mean time you can use a raw github link e.g.

https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Ffoo%2Fbar%2Fmaster%2Fpath-to-sample%2Fazuredeploy.json

Another option would be to mirror the release artifacts somewhere that that has the proper settings or allows you to control them.

[brwilkinson]

@skmkzyk please let us know if this answers your question and query for now?

[skmkzyk]

Yes, I don't have enough knowledge about CORS also, but one solution may loosen CORS restriction to allow Azure Portal to access artifacts on release page directly. How to raise this kind a request to GitHub?

[skmkzyk]

Noted that, the restriction should be '*.portal.azure.com' as some users use some another FQDN than 'portal.azure.com' like 'preview.portal.azure.com'.