Microsoft Azure docs code using deprecated schema? - azure

I am using Microsoft docs Programmatically create Azure dashboards Pasting the dashboard example into VS Code Version: 1.74.3 (user setup)
I get a VS Code Extension (Azure Resource Manager (ARM) Tools v0.15.8) message about the schema being deprecated. I am directed to the github page microsoft/vscode-azurearmtools
However this page and deployment template files are older than the Microsoft docs. So which one is correct?
I ask this because I have an Azure Portal Dashboard deployment (programatical) issue open where my schema is being questioned Azure CLI unable to create portal dashboards from templates #5824

From docs Understand the structure and syntax of ARM templates
"If you're using Visual Studio Code with the Azure Resource Manager tools extension, use the latest version for resource group deployments:
https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#"

Related

azure purview: how to create managed runtime integration programmatically / via API?

Is there any method of creating azure purview managed runtime integration programmatically / via API?
I keep on seeing online resources that showcase how to setup this using purview studio but I would like to figure out how to automate this.
The tech stack I will be using:
Terraform (I have access to both azurerm and azapi provider)
python (I have access to azure SDK for python)
Appreciate your help.
For reference, here is one of the resource that shows how to do this via Azure Studio:
https://thewindowsupdate.com/2022/01/10/azure-purview-managed-vnet-vnet-integration-runtime-and-managed-private-endpoints/

VSS Client SDK doc link is unavailable - https://www.visualstudio.com/docs/integrate/extensions/reference/client/core-sdk

VSS Client SDK doc link is unavailable - https://www.visualstudio.com/docs/integrate/extensions/reference/client/core-sdk
Anyone knows where the new one is?
Thanks,
I found the answer from here.
majority of the Azure DevOps web UI has been converted to new React-based components.
The new Azure DevOps extension sample uses a new Azure DevOps
SDK along with the React-based components in the Azure DevOps UI
library. A full API reference of can be found here
.

Visual Studio Code not finding Subscription for Azure Function Upload

I am evaluating Microsoft Azure. In particular I am interested in Azure Functions.
On my Azure account I get this:
But when I try and upload an Azure Function form Studio Code, I get this:
Does anyone have any idea how I can get out of this loop and upload and tryout Azure Functions?
I would have thought that this functionality would be basic stuff. So I'm convinced I must be doing something wrong, or is it that Microsoft are still catching up with AWS and Google?
According to your description, I think you did not install Azure Functions extension, The Azure Functions extension is included with the the Azure Tools extension pack, if you want to install it, you can visit this link.
Once you've installed the Azure extension, sign into your Azure account by navigating to the Azure explorer, select Sign in to Azure, and follow the prompts.
For more details, you can refer to this official document.

Cloud Explorer fails with "Unable to retrieve child resources"

How to fix this bug?
Open Cloud Explorer (logged in)
Open "Files" folder for some Azure Web App (former Azure Website)
Result:
Cloud Explorer has encountered an unexpected error: Unable to retrieve
child resources.
Details: 'Newtonsoft.Json.Linq.JObject' does not contain a definition
for 'requestNamespace'
I'm using:
Microsoft Visual Studio Community 2015 Version 14.0.25431.01 Update 3
Azure App Service Tools v2.9.6 14.0.21111.0
Common Azure Tools 1.8
Microsoft Azure Tools for Microsoft Visual Studio 2015 - v2.9.41104.6
I had this problem and it was a permissions issue, mine was with a Cosmos Document DB database node.
I had my DevOps guy add me as a contributor to the IAM Azure role and it started working for me. So check all the permissions, and it is the cloud so sometimes you have to give it time to propagate the changes too.
I had this issue when both Azure Storage Emulator and Azure Storage Explorer trying to run at the same time. Try uninstall one or run only one at a time to solve the issue.
Have a look at troubleshooting guide might also help.

Settings up Team Services build to deploy to Azure Web App

I'm trying to create a build in Team Services (Visual Studio Online) but am having a few issues.
My first step is to create a new build and I've selected the template Deployment -> Azure Web App
Then in the build step for Azure Deployment I need to select my Azure subscription. This list is currently empty so I select Manage to add a new one.
Following the instructions here I try to add a new endpoint but it says to select the one called 'Azure' but in my list I've got 'Azure Classic' and 'Azure Resource Manager'. Which one should I use?
I've tried 'Azure Resource Manager' and used the details to generate service key etc using the Powershell script as said in the previous link. Now the status just stay at 'Connecting to service using Service Principal' and is not selectable in the list.
How do I get Team Services to see my Azure subscription?
I must say, I've found the documentation for this a bit lacking in that a lot of the Microsoft sites still use the classic portal or older versions for the sites.
Starting from the end of your question, one of the reasons of that is that some functionality is not available yet on the new portal. As far as i know, all of the functionality should migrate to the new portal in a future.
For Azure Web App, please add the New Service Endpoint using classic mode (and i prefer to do that using certificate - very simple). Then, when adding the web site as the build step (for example), select your added subscription and you should be good to go.

Resources