Anonymous
My feedback
-
23 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.Anonymous
supported this idea
·
-
5 votesAnonymous
supported this idea
·
-
113 votes
repo permissions have begun. We don’t yet have an ETA for preview use, but voting for this feature means you’ll get an invite once we’re ready for some customer validations.
Anonymous
supported this idea
·
-
322 votes
Just to provide an update, we are close to launching a private preview. We are in the final testing stages for this feature. We will have another update in the next few weeks with instructions on how to join the private preview.
Anonymous
supported this idea
·
-
11 votesAnonymous
supported this idea
·
-
8,022 votes
We are looking at options to enable this.
Anonymous
supported this idea
·
-
1,515 votes
At this point our recommendation is to move resources into a new Resource Group with the new name.
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?
-
25 votesAnonymous
supported this idea
·
-
18 votesAnonymous
supported this idea
·
-
95 votesAnonymous
supported this idea
·
-
93 votes
This request is for custom domain and custom SSL certificate support for the IoT Hub endpoint. This work is currently unplanned for IoT Hub but we’re listing to customer requests and may chose to support this in the future.
If you have interest in have a deterministic way of understanding your IoT Hub IP address (and corresponding geo-pair IP address) in order to keep firewall rules up-to-date, see and vote on this request: https://feedback.azure.com/forums/321918-azure-iot/suggestions/15714243-iot-hub-network-address instead.
Anonymous
supported this idea
·
-
4 votes
Device Provisioning Service symmetric key attestation is generally available now. We plan on releasing the C# SDK in the next week or so. Please take a look at our GitHub repo for latest release.
Anonymous
commented
Symmetric key attestation appears to be available in the `preview_provisioningServiceV2` branch on GitHub, but it's yet available as a preview package on Nuget
Anonymous
supported this idea
·
-
6 votes
Thanks for the feedback. Vote this up to let us know how important this is to you.
Anonymous
supported this idea
·
-
36 votesAnonymous
supported this idea
·
-
6 votesAnonymous
supported this idea
·
-
219 votesAnonymous
commented
This has been under review for a long time - are there any updates on this?
Anonymous
supported this idea
·
-
196 votesunplanned ·
AdminSQL Database feature voting forum admins
(Product Owner, Microsoft Azure)
responded
This is not currently planned at this time. Will keep this item open for voting and comments.
Anonymous
commented
One option for this is to use a different schema for each environment, so you can have more than one environment running on a single SQL Database, which saves money.
For example, you can have all your non-Production environments (dev, test, QA) on a single database, with a schema for each, and your Production environment in a database on its own.
-
105 votes
We’ve hit some roadblocks in our design for this feature and will need to re-evaluate options. To help us validate the scenarios we need to address, please continue to share feedback. We will update in the next couple months once we have a better idea of our timeline and approach.
Anonymous
supported this idea
·
Summer has been and gone - any news on this?