Anonymous
My feedback
-
250 votes
Thank you for all the votes. We need more feedback on your scenarios. If you would like to get in touch with us for a discussion, please fill this form: https://aka.ms/ApplicationGatewayCohort
Anonymous
supported this idea
·
-
10 votes
An error occurred while saving the comment Anonymous
supported this idea
·
-
24 votesAnonymous
supported this idea
·
-
31 votesstarted ·
AdminAzure Database for PostgreSQL Product Team
(Product Owner, Microsoft Azure)
responded
pgAudit is now in public preview on Azure Database for PostgreSQL. Thank you for your support of this feature.
For more information: https://docs.microsoft.com/azure/postgresql/concepts-audit
Best,
Rachel, on behalf of the Azure Database for PostgreSQL teamAnonymous
supported this idea
·
-
100 votesAnonymous
supported this idea
·
-
14 votes
An error occurred while saving the comment Anonymous
commented
Also really keen to have at least 1.7.0 on Azure, but really the Azure team needs to commit to keeping extensions updated - at present only 1.3.2 is available, which is more than a year old.
Alternatively, we need a mechanism so users can install their own extensions.
I want to use Azure's Managed Postgres, but you make it so difficult to choose when the extensions are so woefully out of date!
Anonymous
supported this idea
·
-
1,631 votesAnonymous
supported this idea
·
-
29 votes
Based on all the great feedback, we’re adding token based authentication to the repo-based permissions capability. Customers can configure time based tokens, for access to specific repos, with RBAC.
We don’t have an ETA yet, but we expect to be in preview by this summer.An error occurred while saving the comment Anonymous
commented
Gah, the repo-based permissions are only available in the expensive Premium tier - once it's out of preview, will it be available in the other tiers?
An error occurred while saving the comment Anonymous
commented
Summer has been and gone - any news on this?
Anonymous
supported this idea
·
-
11 votesAnonymous
supported this idea
·
-
10 votes
Per the GitHub issue, this is not something we plan to do.
Anonymous
supported this idea
·
-
4 votesAnonymous
supported this idea
·
-
4 votesAnonymous
supported this idea
·
-
4 votesAnonymous
supported this idea
·
-
3 votesAnonymous
supported this idea
·
-
19 votes
We’ve started the design, and would welcome any additional feedback.
Steve
Anonymous
supported this idea
·
-
33 votes
We’ve started the design, and would welcome any additional feedback.
Steve
Anonymous
supported this idea
·
-
7 votesAnonymous
supported this idea
·
-
17 votesAnonymous
supported this idea
·
-
1,694 votes
The Azure Resource Manager team is actively investigating the scenarios around renaming resource groups. To help us better understand the use-cases and to determine which implementations may be viable to address the problem, we would appreciate if you could fill out this 3-minute survey:
https://aka.ms/RgRenamingScenariosAn error occurred while saving the comment Anonymous
commented
Wow, closed after 4 years, and with thousands of votes!
Surely resource groups are identified internally by something like a GUID?
At the very least, couldn't you have a 'rename' feature that behind the scenes just creates a new group, moves resources to it, then deletes the old one?
-
28 votesAnonymous
supported this idea
·
Would be great to get some comment from Azure team about this?