Dan Byrne
My feedback
-
152 votesDan Byrne
supported this idea
·
-
357 votesDan Byrne
supported this idea
·
-
158 votesDan Byrne
supported this idea
·
-
67 votesDan Byrne
supported this idea
·
-
1,760 votes
Thanks for all your feedback so far. This is something we are looking to address relatively soon. Please stay tuned.
Dan Byrne
supported this idea
·
-
600 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 list and also gives us insight into the potential impact of implementing the suggested feature
Dan Byrne
supported this idea
·
-
28 votesDan Byrne
supported this idea
·
-
26 votesDan Byrne
supported this idea
·
-
4 votesDan Byrne
supported this idea
·
-
152 votesDan Byrne
shared this idea
·
-
10 votes
It can be changed via the API. Would that work for you?
An error occurred while saving the comment Dan Byrne
shared this idea
·
-
77 votesDan Byrne
supported this idea
·
-
6 votesDan Byrne
supported this idea
·
-
60 votesDan Byrne
shared this idea
·
-
186 votes
An error occurred while saving the comment Dan Byrne
commented
Agreed - this is a high priority requirement.
An error occurred while saving the comment Dan Byrne
commented
@Tony B - you can do IP filtering on the API itself using Policies
Dan Byrne
supported this idea
·
-
590 votes
An error occurred while saving the comment Dan Byrne
commented
We also request to have the API Management Subscription Keys stored in KeyVault for security purposes
-
3 votes
-
7 votes
Yes that is a reasonable workaround, for scenarios where we absolutely need to make user changes but cannot request this of the user.
It seems like a fairly obvious kind of admin user experience though, to be able to modify user details, so I would hope that this would be available via Azure Portal one day.