My company has an azure tenant, we are mission critical on it.
I want to set up a new subscription within that tenant as a sort of sandbox for some 3rd party activity that needs to be kept mutually isolated from the main subscription. It would be nice if AAD accounts in the tenant could (and would need to) be granted access to the new Subscription. Documentation is unclear, but suggests that the ability to do this is exactly why azure was designed the way it is.
I went to "Subscriptions"; clicked the + for "Add Subscription". I was guided through the process to create a new Subscription, including providing my payment method. When I clicked to complete the process:
- NO new subscription was added
- I am now listed as "Owner" of our EXISTING Subscription
This is bad: I should not be the or an Owner of our company's existing main azure subscription; now it looks like I'm trying to hijack my company. Can you maybe imagine the trouble I might have just set in motion?
How can I please:
- Undo the payment method maneuver to restore it to whatever it previously was, as discreetly as reasonably possible?
- Establish a new subscription within my company's azure tenant for the purpose of doing my required work?
Would someone at Microsoft please NOTE:
- The process in the azure portal to add a Subscription is clear enough and proceeds as expected. However:
- The outcome is totally UNexpected and kind of antithetical to what is clearly indicated
- There is no confirmation dialog/process; if the user believes that the process to "add a Subscription" will do that as every indication along the way sort of validates, then when the user click to perform the addition of the Subscription, no Subscription is added; instead, the user is left to deduce that the payment method they provided for the new Subscription will be charged for the existing Subscription.
- There is no apparent way to reverse or back out of the transaction to which the user has just committed, which is completely different than the one they intended and which azure clearly indicated is exactly what would happen.
I suggest that this is an undesirable, misleading, unfortunate, incorrect process flow that should be corrected.
- I know there are excellent highly trained azure support people, I just have no idea how to reach them intentionally.
- There appears to be no way to directly contact any kind of azure support, including the non-technical account-type support which is headlined as freely available.
- Every option to create a "support request" appears to go through a series of dropdown-list filters. In numerous instances over the past couple of months, I have yet to find a series of choices that even comes close to targeting the issue I want to ask about; including this one. I've gone through all the lists of every issue and sub-issue.
- The only apparent way to actually ask a question, as opposed to click on one from a list that isn't even close, is to submit a question to "the community" as if it's some sort of social media game.
My current question is not a technical support question, yet apparently this is the technical support community, judging by the list of available topics. This is where I landed when I clicked some option for administrative/account/payment questions.
This is disingenuous: to create a "support request" or "ticket" has a well-known commonly understood meaning, which is to direct a specific question to the organizational unit responsible for servicing questions or at least having relevant knowledge, or if nothing else the ability and directive to point people with questions to a closer resource (so that recursively in as few hops as possible the questioner is connected with the appropriate resource). That is not what is possible for azure; what is possible is to "Ask the community"; "see if any other user might have had your exact same issue and already wrote about it in his own words in case that happens to be coherent"; "go search google or bing or stack overflow or something". I can only think that someone at Microsoft understands this distinction.