diff --git a/docs/publishing/other.qmd b/docs/publishing/other.qmd
index 617cdcc565..492cf3a9d5 100644
--- a/docs/publishing/other.qmd
+++ b/docs/publishing/other.qmd
@@ -36,6 +36,10 @@ project:
 
 The recommended workflow for deploying Quarto websites to Site44 is to develop your website in a separate project directory, and then, when it's ready for final publishing, copy the contents of the `_site` directory to the folder for your website.
 
+## Azure {data-link="Azure"}
+
+If you use Microsoft Azure, you can deploy your website to Azure Static Web Apps. It's pretty straight forward. See the article on [Deploy a Hugo site to Azure Static Web Apps](https://learn.microsoft.com/en-us/azure/static-web-apps/publish-hugo#deploy-your-web-app) for additional details by replacing Hugo site part with creating a Quarto website project on GitHub.
+
 ## Amazon S3 {data-link="Amazon S3"}
 
 If you are a user of Amazon Web Services you can serve your website directly from Amazon S3. Note however that this option is a bit more technically involved than GitHub Pages, Netlify, or Site44. See the article on [Hosting a Static Website on Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html) for additional details.
@@ -44,4 +48,4 @@ If you are a user of Amazon Web Services you can serve your website directly fro
 
 Any web server or web host can be used to deploy a Quarto website. Here's a recent [CNET roundup](https://www.cnet.com/web-hosting/) of other web hosts you could consider. You can also deploy a Quarto website on any internal (intranet) web server.
 
-You can also render and publish Quarto websites using a Continuous Integration (CI) service. See the articles on [Publishing with CI](ci.qmd) for additional details.
\ No newline at end of file
+You can also render and publish Quarto websites using a Continuous Integration (CI) service. See the articles on [Publishing with CI](ci.qmd) for additional details.