Microsoft Azure - unable to create "Team Project" using free trail account - azure

I am new to azure and i am trying to create a team project on portal.azure.com and its failing with below error.
The resource group is getting created but team project creation fails
Error:
{"Code":"InvalidRequestValue","Message":"TF400902: There was a failure executing the job. Job Id for the failed creation:b055035e-1b17-480d-a577-abce5d9aff75","Target":"GetProjectJobStatus"}

Reproduce your issue successful with my azure account.
It is not related to the free trail account. If your steps are accurate. (Please refer this blog: Create a VS Online Team Project from the new Azure Portal)
This may coursed by azure. Suggest you try again after several hours.
Update
Even though with this error, I received a successful email from Azure. Please also check whether did you get this email.

Related

Error "Subscription was not found" when trying to create Azure Function App in VS Code

I'm gettting rather weird error when attempting to create new Azure Function App with Azure Functions VS Code extension:
Subscription MY_SUB_GUID_HERE was not found.
No matter what I've tried: reloading VS Code, re-installing Azure Functions extension (incl. older versions), logging out from my MS account in browser, restarting PC, clearing TenantId in VS Code Azure Account extension, removing Azure Functions extension completely including its folder in C:\Users\USER_NAME\.vscode\extensions, signing out and back in via Azure Account extension, creating Azure Function application through the Azure portal incl. new resource group (I've found some old issue on GitHub which supposedly got fixed and one workaround was to create Azure func app through the portal first) - still the same error message, which occurs after selecting location, but actually in VS Code Log (Window) I can see that it fails immediately after 1st step (error code is SubscriptionNotFound + error message above) when you provide a unique name for the application.
At the same time, creating App Service, Resource Group, Static Web App all works like a charm through the corresponding extensions. Of course I see my subscription on Resources pane in VS Code and hence I'm saying that the error is a weird one.
OS: Windows 10 Pro x64 21H1, build 19043.1826
VS Code: 1.69.2
Azure Functions extension: 1.7.4
Azure subscription: free trial
Azure Functions version: ~4
.NET: 6.0
I cannot understand for love of god where the problem is - friend of mine tried it with his Visual Studio Enterprise subscription and it worked without any problem, so perhaps this is an account-related issue? Strange though that other things like App Service seem to work fine. I have "Owner" role for this subscription so it should not be due to the lack of rights or something similar.
Have you updated the az-cli?
e.g. az login or az logout?
What does az account show shows you?
You will be facing this issue because the Azure subscription is absolutely completely empty and the environment could not able to pick up your subscription.
Restart your environment after deploying a sample resource to your subscription.
Now that the subscription is not empty, It will be able to identify your subscription id. Additionally, confirm that your Azure free trial membership has not expired.

Export and edit work items in Azure Devops

I have a problem with exporting and customizing work items in Azure DevOps
when I try to export work items I get this error "The feature is disabled. Contact your Azure DevOps Server administrator. process ID x Project ID x."
I'm the only user in azure DevOps
I tried with tftp tools and witadmin command and both errors were the same.
can anyone help me
Notice: I use Azure DevOps On-premise
when I try to export work items I get this error "The feature is
disabled. Contact your Azure DevOps Server administrator. process ID x
Project ID x
To achieve the above requirement ,
As you are user,
First of all you need to have an administrator permissions to your project.
Then we can export the project .
Based on this Prequisite as described on MS DOC well: -
To get those permissions you can refer this MS DOC.
For more information please refer this MICROSOFT DOCUMENTATION

Azure pipelines not running

I've got a free tier Azure Cloud Account. I used to have a project and requested a free agent for running pipelines. All was ok.
I deleted that project and created a new one.
I'm now trying to create a very basic Hello World kind of pipeline and getting it to run, to test things. The pipeline fails to run with the error below.
Error Message: No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request
I can see in my organization settings that I have that free agent available and 1800 mins/month of run time available. But i think that agent isn't getting used/found by my pipeline jobs.
I'm a noob at azure, so pardon me for any goof ups in the question.
You just write message to https://aka.ms/azpipelines-parallelism-request with your name, email, project etc. and after 24-48 hours you can run your pipeline
Microsoft comes with some temporary alternative approach until the automate is implemented to grant the permission for those users who requires the free hosted agent pools.
Now users needs to be drop the email to get the free tier access based on the project visibility types.
There is not a standard timeline for approval which someone can predict approval in days, but by considering the mass requests and manual approval process we can consider the timeline of 7 to 15 working days from your email.
For More information -> https://devblogs.microsoft.com/devops/change-in-azure-pipelines-grant-for-private-projects/
Solution: Just after posting this question, I thought of creating another project and make it private. I then ran a sample pipeline and it worked. So basically, my issue was that the pipeline granted to me was for a private project and not a public one. I had forgotten about it as i was revising azure after some time.

Azure Devops release pipeline unauthorized for some projects

I am trying to release multiple projects in 1 solution using Azure Release pipeline
They are all connected to the same Azure Subscription, but some do deploy to the given app service while others give an unauthorized error.
Ive looked into it and i read that adding website_webdeploy_use_scm to the app service should help the Unauthorized error, but this didnt help for me.
What else could i look at? I connect through Azure Devops so i just selected the subscription from the list it automatically gathers from Azure because im logged in using the same logins as i use for Azure Portal
the full error is:
Connected to the remote computer ("xxxx.azurewebsites.windows.net") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
Error: The remote server returned an error: (401) Unauthorized.
according to the error I'd suggest you check service principal permissions. it probably lacks the permissions required to manage those webapps.
So after refresh publishing profile in Azure Portal and trying it again it fixed itself so im not sure if that caused it or not but it worked!
another fix is to delete the slot and make it again

No Longer Able to Deploy VirtoCommerce from GitHub

In the past I have successfully deployed VirtoCommerce to Azure from GitHub using the "Deploy to Azure" button. But today, using my Azure free trial subscription, I am receiving an error message.
Using the "Free" SKU, when I attempt to deploy, it gets to the "Configuring SQL Server Firewall Rules" step and then fails with deployment error, "The operation is not supported for your subscription offer type".
Does this no longer work with a free trial account? As I said, it worked before, so something must have changed.
This is because the Web edition of the Azure SQL Database is now retired.
I have changed the database edition to the Basic (the new minimal edition) in azuredeploy.json, so now everything should work again.

Resources