Skip to content

Commit

Permalink
Added Microsoft Support statement (Azure#325)
Browse files Browse the repository at this point in the history
* Added Microsoft Support statement

* Updated based on kwill-msft review
  • Loading branch information
adrianhall committed Jul 10, 2023
1 parent d7ba1a9 commit 3391894
Showing 1 changed file with 14 additions and 3 deletions.
17 changes: 14 additions & 3 deletions SUPPORT.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,18 @@
# Support

This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new Issue.

## Microsoft Support Policy

Support for this content is limited to the resources listed above.
If issues are encountered when deploying this reference implemenation, users can engage Microsoft support via their usual channels. Please provide correlation IDs where possible when contacting support. For instructions on how to obtain deployments and correlation Ids, see [View deployment history with Azure Resource Manager](https://learn.microsoft.com/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal#get-deployments-and-correlation-id).

The following list of issues is within the scope of Microsoft Support:

* Portal deployment of the reference implmentation.
* Underlying resource or resource provider issues when deploying the template.
* Subscription creation via the Azure portal.
* ARM deployment issues (e.g. template validation, CheckAccess API).

Any issues that are deemed outside of the above list by Microsoft Support or requires bugfix in the reference implementation will be referred to GitHub issues.

## How to file issues and get help

This project uses [GitHub Issues](https://github.com/azure/reliable-web-app-pattern-dotnet/issues) to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicated.

0 comments on commit 3391894

Please sign in to comment.