Hakan Lindestaf
My feedback
-
4 votes
Hakan Lindestaf shared this idea ·
-
164 votes
We have done a lot of progress on this area in last few years, and we would like to know if there is something scenario specific that you guys are looking for?
Thanks,
Azure Portal TeamHakan Lindestaf supported this idea ·
-
625 votes
SSL only requires multiple IPs when the client is on Windows XP, using an older version of Internet Explorer. Most modern browsers support SNI (Server Name Indication) and thus don’t require multiple IPs.
Support for multiple IPs is under review in the team.
Hakan Lindestaf supported this idea ·
-
2 votes
Hakan Lindestaf shared this idea ·
An error occurred while saving the comment -
1 vote
Apologies for how long it has taken us to respond. The Azure Billing team was reorganized recently. The new team is focused on understanding and fixing current issues, and engaging with the community.
Thanks for your feedback. To enable what you suggest we’d need to have a user authorize specific other users to use their credit card. We;ll look into the feasibility of building this feature.
An error occurred while saving the comment Hakan Lindestaf commented
I don't know if you need to manage that, if User A has authorized User B to use their credit card (corporate shared card) then I think User B is already authorized, it's not something you have to manage. It's like I'm using the same CC at both Microsoft and at Amazon, two different services, should not be any need to check if the card is used at both places (and I realize these two services are under Microsoft, it was just an example that the same card can be used at multiple places)
Hakan Lindestaf shared this idea ·
-
295 votesunder review ·
AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
This is something that we are evaluating now for a future Azure update.
Hakan Lindestaf supported this idea ·
-
29 votes
I like this idea. Let’s increase the vote count and i think we could build this.
Hakan Lindestaf supported this idea ·
-
29 votesunder review · 0 comments · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →
Hakan Lindestaf supported this idea ·
-
57 votes
We’re constantly making improvements to the deployment times for Windows Azure.
Hakan Lindestaf supported this idea ·
-
38 votesunder review · 1 comment · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →
Hakan Lindestaf supported this idea ·
-
47 votes
This functionality is coming soon in the platform; stay tuned.
An error occurred while saving the comment Hakan Lindestaf commented
It would be better to administer it through the portal so we don't have to deploy new versions if the restrictions change. (I'm thinking DEV instances of web sites, etc that I want to restrict access to).
Hakan Lindestaf supported this idea ·
-
289 votes
Good idea.
Hakan Lindestaf supported this idea ·
-
400 votesunder review · 7 comments · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →
Hakan Lindestaf supported this idea ·
-
5 votes
You’re right, this pop-up feature is of limited use to customers in your situation. We are planning on fixing this, though we don’t have a current timeframe for this.
-Adam (Azure Billing Team)
Hakan Lindestaf supported this idea ·
-
11 votes
Thanks for the feedback Hakan, we’ll look into this.
Hakan Lindestaf shared this idea ·
-
20 votes
Could you tell me a little bit more about your application pattern – how many roles do you have per cloud service? Do the cloud services that you would like to restart have any dependencies on one another? If not, have you tried restarting the cloud services in parallel?
An error occurred while saving the comment Hakan Lindestaf commented
I'm using Octopus Deploy for release management and they way it's (currently) designed is to run one task at a time, and one task is to upgrade one cloud service. So it has to go through them one by one. I'm not sure what you mean with roles, I have in general 1 instance per cloud service and I'm using the production/staging pattern with vip swap (but that's not really relevant to this issue). There are no dependencies, but note that I'm not *restarting*, I'm upgrading the code with a new deployment package.
Currently it requires Premium Azure AD at $6/user/month, just to assign a user as local admin is way too expensive IMHO.