Update deploying-to-azure-static-web-app.md

[blueboxes]

Updated to use the newly released v1 actions (as per template in azure) and set permissions to allow a comment to be written to the PR.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md	fpt ghec ghes@ 3.10 3.9 3.8 3.7 3.6 ghae	fpt ghec ghes@ 3.10 3.9 3.8 3.7 3.6 ghae

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

[cmwilson21]

@blueboxes Thanks so much for submitting a PR! I'll get this triaged for review ⚡

[SiaraMist]

Hi @blueboxes, thank you so much for submitting this PR! ✨ I definitely understand why you are updating this workflow to use v1 instead of pinning to a commit SHA. However, per our style guide, for third party actions we always pin to a commit SHA to comply with our security recommendations. If it helps at all, we include a note at the top of workflows that do this to help explain why. I'm going to close out this PR, and if you want to further contribute to our docs, please check out our help wanted board, where we have open issues to improve our docs. Thank you again!

[SiaraMist]

I just saw the permissions you added, so I updated the PR so I can accept that update to the example! Apologies for not catching that earlier. Thank you for your help improving the docs! I'll go ahead and get this merged.

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡