Customers with an Azure support plan can open an Azure support ticket. We recommend this option if your problem requires immediate attention.
We use GitHub Issues to track bugs, questions, and feature requests. GitHub issues are free, but response time is not guaranteed. See GitHub issues support process for more details.
To ensure the relevance and manageability of our issue queue, we have an automated process that will close issues that are over two years old and have not been updated in the last 30 days. This measure is designed to help us respond to and resolve current issues more efficiently. We appreciate your understanding and cooperation in maintaining a focused and up-to-date issue tracking system.
- Take a look at the Azure SDK blog.
- Search for similar issues in our GitHub repository
- Chat with other community members on gitter
- Ask a question on StackOverflow and tag it with azure-sdk-js
- Share or upvote feature requests on Feedback Page.
- Ask a question on Twitter
- Ask a question at Microsoft Q&A
- Ask a question at Microsoft Tech Community
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center(secure@microsoft.com). You should receive a response within 24 hours. Further information, including the MSRC PGP key, can be found in the Security TechCenter
The Azure SDK libraries for JavaScript will not be guaranteed to work on Node.js versions that have reached their end of life. Dropping support for such Node.js versions may be done without increasing the major version of the Azure SDK libraries.
We will announce Node.js engine support changes 3 to 6 months beforehand via:
- The Azure SDK Blog.
- A pinned issue.
We strongly recommend migration to LTS versions of Node.js to be eligible for technical support. In terms of browsers, we support latest versions of Safari, Chrome, Edge and Firefox.
Please refer to Azure SDK Support and Lifecycle information for more on our support policy.