Forum Widgets
Latest Discussions
Set multiple values in devops library variable
Hi I need to pass multiple values in Library variable in DevOps. Currently my YAML looks like below. Contents: | RepoFolder1\*.txt RepoFolder2\*.csv RepoFolder3\*.py I want to create variable and pass above values to library variable in DevOps like below. Contents: $(Source_Files) Somehow Library variable is plain text, and it is not allowing multiline. How to achieve this. Thanks, Siva.
Azure Billing Credit - No Explanation
Hello, I have a customer who received a larger credit on their February bill without any explanation. The customer is seeking clarification on the reason behind this credit. We compared the Azure billing and Azure portal cost management and noticed discrepancies in charges for compute and some PaaS services. Unfortunately, support has not been able to provide any answers or assistance. Could you please suggest a way to identify the source of this credit and the reason for it? Is there a specific team or group that might be able to assist us in resolving this issue? Thank you in advance for your help! Terru
'Azure NPS Extension for Azure MFA' licensing
We have interest in installing the Azure NPS extension for Azure MFA to protect our on premise remote access VPN solution. This VPN solution is a simple firewall that provides remote access (client) VPN to our users and is used in combination with our local Win2019 Network Policy Server which acts as radius to enable the users to authenticate with their AD credentials. Those AD credentials are also synced from our local AD to Azure AD Free using Azure AD connect. I'm trying to determine if I need extra licensing for the extension. The documentation says: "The NPS Extension for Microsoft Entra multifactor authentication is available to customers with licenses for Microsoft Entra multifactor authentication" When I click that last link it has a table that, amongst other things, says it's available to "All Microsoft 365 plans" Most of our users have Exchange Online plans, some users have Office 365 Business standard plans. Both user groups already have MFA enabled and working when for example, logging in to Outlook webmail https://outlook.office.com with their synced AD identity. Do we need extra licenses in order to install and use Azure NPS extension for Azure MFA or not? Thanks in advanceAzure Event Grid Domain Creation: Overcoming AZ CLI's TLS Parameter Limitations with Workaround
Introduction: The Intersection of Security Policies and DevOps Automation In the modern cloud landscape, organizations increasingly enforce strict security requirements through platform policies. One common requirement is mandating latest TLS versions for example TLS 1.2 across all deployed resources to protect data in transit. While this is an excellent security practice, it can sometimes conflict with the available configuration options in deployment tools, particularly in the Azure CLI. This blog explores a specific scenario that many Azure DevOps teams encounter: how to deploy an Azure Event Grid domain when your organization has a custom policy requiring latest version considering TLS 1.2, but the Azure CLI command doesn't provide a parameter to configure this setting. The Problem: Understanding the Gap Between Policy and Tooling What Is Azure Event Grid? Azure Event Grid is a serverless event routing service that enables event-driven architectures. It manages the routing of events from various sources (like Azure services, custom applications, or SaaS products) to different handlers such as Azure Functions, Logic Apps, or custom webhooks. An Event Grid domain provides a custom topic endpoint that can receive events from multiple sources, offering a way to organize and manage events at scale. The Policy Requirement: Many organizations implement Azure Policy to enforce security standards across their cloud infrastructure. A common policy might look like this: { "policyRule": { "if": { "allOf": [ { "field": "type", "equals": "Microsoft.EventGrid/domains" }, { "anyOf": [ { "field": "Microsoft.EventGrid/domains/minimumTlsVersion", "exists": false }, { "field": "Microsoft.EventGrid/domains/minimumTlsVersion", "notEquals": "1.2" } ] } ] }, "then": { "effect": "deny" } } } This policy blocks the creation of any Event Grid domain that doesn't explicitly set TLS 1.2 as the minimum TLS version. The CLI Limitation: Now, let's examine the Azure CLI command to create an Event Grid domain: az eventgrid domain | Microsoft Learn TLS property is unrecognized with the latest version of AZ CLI version. Current Status of This Limitation: It's worth noting that this limitation has been recognized by the Azure team. There is an official GitHub feature request tracking this issue, which you can find at => Please add TLS support while creation of Azure Event Grid domain through CLI · Issue #31278 · Azure/azure-cli Before implementing this workaround described in this article, I recommend checking the current status of this feature request. The Azure CLI is continuously evolving, and by the time you're reading this, the limitation might have been addressed. However, as of April 2025, this remains a known limitation in the Azure CLI, necessitating the alternative approach outlined below. Why This Matters: This limitation becomes particularly problematic in CI/CD pipelines or Infrastructure as Code (IaC) scenarios where you want to automate the deployment of Event Grid domain resources. Workaround: You can utilize below ARM template and deploy it through AZ CLI in your deployment pipeline as below: Working ARM template: { "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { "domainName": { "type": "string", "metadata": { "description": "Name of the Event Grid Domain" } }, "location": { "type": "string", "defaultValue": "[resourceGroup().location]", "metadata": { "description": "Azure region for the domain" } } }, "resources": [ { "type": "Microsoft.EventGrid/domains", "apiVersion": "2025-02-15", "name": "[parameters('domainName')]", "location": "[parameters('location')]", "properties": { "minimumTlsVersionAllowed": "1.2" } } ] } Please note I've used latest API version from below official Microsoft documentation : Microsoft.EventGrid/domains - Bicep, ARM template & Terraform AzAPI reference | Microsoft Learn Working AZ CLI command: az deployment group create --resource-group <rg> --template-file <armtemplate.json> --parameters domainName=<event grid domain name> You can store this ARM template in your configuration directory with replacement for Azure CLI command. It explicitly sets TLS 1.2 for Event Grid domains, ensuring security compliance where the CLI lacks this parameter. For example: az deployment group create --resource-group <rg> --template-file ./config/<armtemplate.json> --parameters domainName=<event grid domain name> Disclaimer: The sample scripts provided in this article are provided AS IS without warranty of any kind. The author is not responsible for any issues, damages, or problems that may arise from using these scripts. Users should thoroughly test any implementation in their environment before deploying to production. Azure services and APIs may change over time, which could affect the functionality of the provided scripts. Always refer to the latest Azure documentation for the most up-to-date information. Thanks for reading this blog! I hope you've found this workaround valuable for addressing the Event Grid domain TLS parameter limitation in Azure CLI. 😊
Error BCP036: The property "gateway" expected a value of type "string"
We're getting the error when we're trying to deploy On Premise Data Gateway API Connection: Error BCP036: The property "gateway" expected a value of type "string" but the provided value is of type "object" This was the initial properties file of the API connection we're trying to deploy We then updated the value of the gateway property into a string But got this error "ConnectionGatewayReferenceMissing","message":"The gateway reference connection parameter is missing for the on-premise connection request." Are we missing an attribute? This never happened before. It looks like there have been changes that happened some time this week to Azure API connection deployment
search/codesearchresults not able to get more than 2000 results?
when I send a POST API request to "https://MYAZUREINSTANCE/tfs/COLLECTION/MYPROJECT/_apis/search/codesearchresults?api-version=7.0" with this payload { "searchText": "ext:dll", "$skip": 1000, "$top": 1000, "filters": [ { "name": "ProjectFilters", "values": [ "MYPROJECT" ] }, { "name": "RepositoryFilters", "values": [ "$/MYPROJECT" ] } ], "searchFilters": { "ProjectFilters": [ "MYPROJECT" ], "RepositoryFilters": [ "$/MYPROJECT" ] } } the API returns the file data correctly. but I have more than 2000 such files. if I set "$skip": 2000, it returns an error stating that the $skip must be between 0 and 1000.... How do I get the rest of the files?
Azure Devops Pipelines Stage Release
Hi! This is the problem I have! I'm making a process that collects many applications from a repository, which are eventually compiled into docker containers. And after assembly, I install them on various stands (dev, test, and so on). But I can’t select the branch in the releases from which the application will be built. Therefore, I thought that pipelines have such an opportunity at launch. Ability to select a Git branch. But I came across the fact that when I create a pipeline, not a release, my tasks are performed sequentially or with dependencies on each other. In this situation, I cannot restart the same pipeline only with different parameters. Let's say I have an assembly stage, a launch stage for a dev bench, and a launch stage for a test bench. If I start rolling on the dev stand, then I cannot restart the same pipeline and roll on the test stand. Maybe I don't know something? Have you encountered such a problem? Maybe there is a solution (it’s possible in Git Lab).Regarding changing the git push timestamp on azure repository
Hi! I had first used git rebase for editing the particular committer and saved and proceeded with GIT_COMMITTER_DATE="2025-04-10T15:30:00" git commit --amend --no-edit --date "2025-04-10T15:30:00" like this and used another code to make the author date and committer date to be same and then I pushed to the remote repository like azure devops. After changes I can see the committer date gets changed as expected and author date too changed and I made them the same .But my question is in azure devops there is showing three dates commitor date,author date,push date,In my case for example as per code commuter date is 2025-04-10T15:30:00;authored date is 2025-04-10T15:30:00 while the push date is not that and it was the time I pushed to devops. In devops in the commit history section the timestamp is changed while when I go to the push section of devops the timestamp is showing not the commit timestamp but the time when I actually pushed to there repo.My question is I have done the change for commt,author date but I cant do for the push date.Is there any way to change the git push date or devops push date timestamp in the repository. Hope I get the required information.Thank you
Error 500 logging into ADO or Private Nuget feed
I have a long standing user who in the middle of last week lost his ability to login got ADO or connect to our private feeds getting an 500 Internal Server Error. The situation is complicated slightly in that we share an ADO Subscription amongst multiple tenants so this use is added as an ExternalAzureAD Guest. I dropped and recreated the user both in ADO and his guest account in the ADO joined tenant, waited half an hour and then re-added the user with to ADO, but still the same error. I have done the same with a scratch user and all this works without issue. When the user goes direct to the private feed and logs in, they get the error: {"$id":"1","innerException":null,"message":"TF400813: The user '66faf51b-bf86-6913-bd44-d1b38246c0ea' is not authorized to access this resource.","typeName":"Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, Microsoft.TeamFoundation.Framework.Server","typeKey":"UnauthorizedRequestException","errorCode":0,"eventId":3000} When they try to login to ADO, the get the attached error: We tried this on a different machine and got the same behaviour, so it seems account related. How can I resolve this?
