Skip Navigation

Azure Community Support

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


    MSDN Forum

    Microsoft response to Azure technical questions

    1. Most Recent
    2. Popular
    3. Trending
    Azure Feedback

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

    1. Most Recent
    2. Popular
    3. Trending

    Please help get these people out of my life you know the build that REgions built and paid for through my money You are not in the guidelins

    Someone needs to help the innocent when they do a build from Azure to remote control you you are not within Microsoft code of ethics Please help You know the one that was paid for by Regions Bank 1st check for 75,000 and then 10,000 and then my investment money ran through Regions Morgan Keegan Teust as well

    fix hot fix patches that disable the environment

    Hot fix patches that cause 36 hour outages make this an un-viable solution for my team and my client.

    My Texas Divorce Lawyer

    URL: Keywords or tags: lawyer, divorce, attorney, family law Description: My Texas Divorce Lawyer helps clients in Texas who are facing a divorce or family law legal issues. If you need help with divorce, child custody, child support, divorce mediation, grandparent's rights, or other family law issues, then give our office a call to set up an initial consultation. Owner Name: Aaron Sanchez Full Address: 2625 Harmony Park Crossing, #1232 Spring, TX 77386 Phone: (832) 390-4414 Business Email: Year Found: 2017 Number of Employee: 2 Operating Hours: 24/7 Video URL: Social Media Links (GooglePlus, Facebook, Twitter etc..):

    Date format inconsistencies in Azure documentation

    The date of articles are not in the same format in Azure Documentation, where: Some use Day/Month/Year, like 24/09/2018: While others use Month/Day/Year, like 07/17/2018: Was this article published (11/05/2018) May 11th, 2018 or November 5th, 2018? Please document which date format is used in the Azure documentation to remove confusion and bring consistency. Using ISO-8601 date format YYYY-MM-DD and documenting the date format used in Azure documentation would resolve this issue.

    File a support ticket

    Tweet at us @AzureSupport

    Help us improve. Is this page helpful?

    160 character limit