The Wayback Machine - https://web.archive.org/web/20200401215236/https://azure.microsoft.com/en-us/support/community/

Azure Community Support

Ask questions, get answers and connect with Microsoft engineers and Azure community experts

Products

    MSDN Forum

    Microsoft response to Azure technical questions

    Error Code 80070520

    Forum: Azure App Configuration

    SQL DataSync - Agent Schema

    Forum: Azure SQL Database

    issues with Azure AD Sync

    Forum: Azure Migrate

    Azure Feedback

    Do you have an idea or suggestion based on your experience with Azure?

    give examples for the fields and or parameters and have a page regarding considerations for each connector / action and their fields

    give examples for the fields and or parameters and have a page regarding considerations for each connector / action and their fields telling what kinds of inputs will and won't work

    When creating a new devops project with GIT, it shouldn't be mandatory to buy WebApp or VM

    When creating a new devops, you have 2 options: 1 - Create a new project with WebApp or VM (comes with GIT repository) 2 - Bring your own code The problem with the first option is that it forces you to buy a WebApp or a VM. The problem with the second option is that, although it gives you the liberty to make your deploy to a proprietary server, it doesn't bring an Azure GIT repository. You have to have a GitHub. There should be an option that would bring exclusively Git + DevOps.

    Automation Automation Satus "New" is in use, but not implemented in modules an documentation

    Azure Automation jobs uses status "New" before jobs go into "Queued". This is named here under the example for concurrent jobs : https://docs.microsoft.com/en-us/azure/automation/automation-runbook-execution But it is nowhere to be found on the list of possible statuses for automation account jobs. This is also true for the "AzAutomationJob-modules" It is not accepted as a possible input for -Status

    CDN purge authentication API

    When purging CDN endpoint using API call, in authentication usually we need to get auth code manually first. We checked the API has only delegated permission, thus OAuth 2.0 client credentials grant flow cannot be used. Now our customer have the demand that using API to get auth code then use the code to process the purging process instead of using browser to get auth code. Please consider to implement it if possible. Thank you!

    File a support ticket

    Create an incident

    Tweet at us @AzureSupport

    Connect on Twitter

    Help us improve. Is this page helpful?

    160 character limit