Taking the Billing tile on the dashboard: the billing information is being automatically cycled between the subscriptions, but it would be good if the user could just cycle between them or pause the auto-cycling.11 votes
The title of the portal should include the number of unread notifications (much like a number of webmail sites do for new emails).
Furthermore, if your browser supports W3C Web Notifications ( http://www.w3.org/TR/notifications/ ) we should be using those too.11 votes
We utilise Locks on various resources to stop our core development and production resources being accidentally deleted, however, the same ability to apply a lock to Azure App Registrations in AAD would be beneficial10 votes
Important announce is not use blog, but should use notification in azure.
Now, I can not use TCP 25port because I migrated subscription to MSDN.
If this announce would be not blog, but would be notification in azure, I didn't migrate my subscription.
I hope important announce will be notification in azure because I can not notice blog released.10 votes
It would be useful if we could assign a background color to tiles. This could be used in visualizing/categorizing services, customers or various deployment stages. Imagination really.
See attached screenshot.
Mabye as a start?10 votes
Azure Resource Policy is a great feature for enterprise customers to enforce their resources in a compliant state. However, there is no user interface to view policy definitions and assignments in a given scope. Also, the UI don't respect policy at all but only give an error after the deployment is submitted.10 votes
We’ll definitely do this
The portal shows that "Something went wrong," but really, that's not helpful. I think it's trying to show a virtual machine that no longer exists, but how is anyone supposed to figure that out if the message is as vague as "something."10 votes
It should be possible to export a current resource group deployment as a terraform file, azure cli statements or azure powershell statements.9 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
It should be possible to manage group policies from Azure.
As per the comments at the bottom of this thread, it's not possible.
It would be great if the URLs to the portal contained Tenant's name / ID, because when you share it to external co-workers, they would get switched to the correct tenant and subscriptions.
So instead of having:
you would have:
To help comply with anti-doxxing patterns, it would be nice to have the option to hide email in the upper right hand corner of the screen.
I'm recording/streaming coding content and wish to show some Azure work without giving away my email. Options like "Name only", "Name and Email", or "Email only" would save me a lot of effort9 votes
I again post feedback along with previous post; https://feedback.azure.com/forums/223579-azure-portal/suggestions/18363238-put-newline-in-activity-log-description
It is extremely uncomfortable to read description!9 votes
Currently resources can't be renamed unless redeployed.9 votes
Direct GitHub access from within Azure Portal for downloading/uploading or synchronizing ARM templates between Azure Portal and GitHub.9 votes
You can import quickstart templates by going to New, search for “template deployment”, edit the template, and import a quickstart template from there.
We can add the ability to upload to GitHub, if that’s valuable to a lot of people.
When there is multiple blades/panes open and the horizontal scroll bar shows up, it woule be good if we can scroll from left to right using the vertical mouse scroll wheel.
If the blade/pane under the cursor has content that needs to be vertically scrolled, vertical scroll has the priority, once it reaches the limit, then scroll horizontally depending on the direction.9 votes
We can consider this
When using a shared dashboard and just testing changes/and or just wanting to change the timespan temporarily, the dashboard says there are unpublished changes and this blocks MANY features, like being able to make further edits, full screen, SEARCH, etc. There is no reason for a change to block so many features, especially if I want the change just locally for a short time.8 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
I suggest that a "Impersonate" feature be added for portal administrators. Like in ServiceNow, this feature would allow an administrator to test the permissions/role granted to users within a group. This would allow the admin to see exactly what the user is sees.8 votes
When viewing the list of users in a group it looks like users are sorted by the order they where added to the group. Please add the ability for customized sorting, e.g. by username.8 votes
The Always On feature in App Services is designed to prevent IIS from sleeping by continually pinging the web endpoint. This works by sending a request to the app service endpoint, port 80, root path (/) but in several scenarios, this doesn't work. 1) If the service is https only 2) If traffic manager is protecting the sites, then TM pings it anyway and always on will instead route via TM and possibly not do what it should do. 3) If the root path is not available (e.g. one of my WCF services doesn't have anything at the root) then it also fails.
The net sum is a lot of log noise. It could include more messages such as "always on is not available when using Traffic Manager" and it could also ping port 443 if the app is https only and maybe the help info could say it only works on the root path or allow it to be configured?
The Always On feature in App Services is designed to prevent IIS from sleeping by continually pinging the web endpoint. This works by sending a request to the app service endpoint, port 80, root path (/) but in several scenarios, this doesn't work. 1) If the service is https only 2) If traffic manager is protecting the sites, then TM pings it anyway and always on will instead route via TM and possibly not do what it should do. 3) If the root path is not available (e.g. one of my WCF services doesn't have anything at the root) then…8 votes
BUG: HTTP error 400. The size of the request headers is too long
Azure portal has a bug which ften returns only a blank page with:
HTTP error 400. The size of the request headers is too long
The problem seems to be related to a cookies named OpenIdConnect.nonce.* . If I clena them this will work fine till next time...
Patrick Marques8 votes
- Don't see your idea?