Azure DevOps: Why is my subscription not shown when creating a new service connection?
Apr 12
I am using Azure DevOps with a Microsoft Account (@outlook.com). The same account is co-administrator of 3 different Azure Subscriptions.
I am trying to create a new Service connection from my Azure DevOps Project to my newest Azure Subscription (out of the 3).
When I:
- Go to my project's Project Settings view and click on the Service Connections tab.
- Click on the 'New service connection' button.
- Choose 'Azure Resource Manager' for the connection type.
- Choose 'Service Principal (automatic)' authentication method.
I find that the drop-down list for Subscription is only showing my two older subscriptions and my newer subscription is missing, as shown here:
How can I get my third, newer, subscription to appear in the 'Subscription' list?
I've tried the following without success:
- Made my Microsoft Account to be a 'Co-administrator' of the Azure Subscription.
- Gave my Microsoft Account the 'Owner' Role for the Azure Subscription.
- Added my Microsoft Account to the 'Global Administrators' group in Azure Active Directory.
- Set 'Guest users permissions are limited' to 'No' in the In my Active Directory's External collaboration settings.
UPDATE: The subscription that's not shown in the list is currently a "free-tier" subscription whereas the 2 subscriptions that are shown are "pay-to-go". Could this be the reason for my problem?
azure
1 answer
Accepted answer · original discussion
Apr 15
I can finally see my Azure Subscription in the Subscription list. I'm not 100% sure which step I took is responsible for fixing the issue so I'll list 2 things that I did:
In the Azure Portal I created a new App Registration, this time having the "Supported account types" setting set to "Accounts in any organizational directory ... and personal Microsoft account ...":
In PowerShell and using the AzureAD module I reset the Service Principal Key Credential:
a. Ran PowerShell (v5.1) "as Administrator".
b.
Install-Module -Name AzureADc.
Connect-AzureAD -TenantId <tenant-id-from-the-app-registration-overview>b.
New-AzureADServicePrincipalKeyCredential -ObjectId <object-id-from-the-managed-application-overview>
PS - The Subscription's being in the free-tier seems to be irrelevant to the issue.
2 question comments
Use comments to ask for clarification. Post a solution as an answer.
Apr 12
Apr 12