Are you experiencing a rendering issue in the Azure Portal?
This is how you make sure the support team gets all the information they need to troubleshoot your issue
Start with the basics
Go through the following sanity checks if you see a rendering issue in the Azure Portal:
- Try again in an InPrivate/Incognito window
- Try again in a different browser
- (if applicable) try again with a different user account
- Try again from a different device
- Try again from a different network (for example: share your phone’s connection)
If the issue still occurs, it needs to be reported in an Azure support case.
Take full screen screenshots
Take several full screen screenshots documenting the issue that you are experiencing. Full screen screenshots help the support team to understand what options you are choosing in which order. This is important to establish if the issue is reproducible.
The Snip tool on Windows allows you to take great screenshots of the entire screen, separate windows, or elements of a window. https://mix.office.com/Snip
On a Mac you can take full screen screenshot by hitting cmd + shift + 3 for the whole screen or cmd + shift + 4 for a certain window. https://support.apple.com/en-us/HT201361
For Linux distributions running a desktop, check with your distributor. (for example: Ubuntu http://tips.webdesign10.com/how-to-take-a-screenshot-on-ubuntu-linux)
Take a packet trace (Fiddler)
To get a full understanding of what is causing the issue that you are experiencing a packet trace will be required.
To make sure all the required information is captured, HTTPS traffic needs to be decrypted.
On Windows you can use the Fiddler tool to create your packet trace http://www.telerik.com/fiddler
If you are using Fiddler, be sure to configure it to decrypt HTTPS traffic. http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/DecryptHTTPS
To enable the decryption, Fiddler installs a root certificate. You may not be allowed to do this on a corporate account due to your company’s group policy settings.
If you are unable to use the Fiddler tool, or if you are on a Linux or Mac device, you can use your browser to create the packet trace and save it as a XML or HAR file.
When conducting a packet trace, make sure you are doing it in an InPrivate/Incognito window and that any unnecessary background tasks or browser tabs/windows are closed.
Start by enabling the developer tools in your browser and select the “Network” or “Tracing” option.
Make sure logs are being preserved and that the log is cleared when you start the process.
Go to “portal.azure.com”, log in, and reproduce your issue. Once everything has been captured, log back out and wait for any running requests to complete. Then proceed to save the trace as HAR, or XML.
If you are using Fiddler for your trace, simply save it as a SAZ file once it is complete.
File your support case
Log in at https://azure.microsoft.com/en-us/support/plans/ or contact Premier Support (if you have it)
In Azure Portal go to Help & Support and choose to create a case. Indicate that your problem is with the Azure Portal.
You can attach the screenshots and the collected diagnostics data as a zip file.
Please provide as much detail about your issue as you can. For portal rendering issue, it is important to know what exact options you are choosing before the issue occurs.