Azure Serial Console issue and feature tracking

Overview

This repository is offered for tracking features and issues with the Azure Serial Console. This repository is monitored by the Azure Serial Console product team in order to engage with our community and discuss questions, customer scenarios, or feature requests.

Support through issues on this repository is provided on a best-effort basis (see Bug Guidance below). To receive urgent support you must file a support request through official Azure support channels as urgent support is explicitly out of scope of this repository's objectives.

IMPORTANT: For official customer support with response-time SLAs please see Azure Support options.

Important links

• Documentation for using Azure Serial Console with Linux VMs: http://aka.ms/serialconsolelinux
• Documentation for using Azure Serial Console with Windows VMs: http://aka.ms/serialconsolewindows
• Updates about the service, including new features and new Azure regions: Azure Serial Console feed in Azure Updates

Code of conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Bug Reports

IMPORTANT: An inability to meet the below requirements for bug reports are subject to being closed by maintainers and routed to official Azure support channels to provide the proper support experience to resolve user issues.

Bug reports filed on this repository should follow the default issue template that is shown when opening a new issue. At a bare minimum, issues reported on this repository must contain the following information:

• A good title: Clear, relevant and descriptive - so that a general idea of the problem can be grasped immediately
• Description: Before you go into the detail of steps to replicate the issue, you need a brief description.
  • Assume that whomever is reading the report is unfamiliar with the issue/system in question
• Be sure to include any supporting information you might have that could aid the developers.
  • This includes exact commands used, screenshots, etc.