Azure DevOps Yaml Pipeline Build Validation Across Multiple Repos
I have multiple repos that are configured the same way for unit tests. (repo1, repo2, repo3). I then have a separate repo that includes the infrastructure for the tests (repo-tests). It has a docker-compose file, set's all the needed environment variables, image, etc. I can clone down all 4 repos, specify the repo that I want to test and run the docker-compose up and it does all the unit tests. What I'm trying to do is build out a Yaml build pipeline in ADO and save the code for the pipeline in repo-tests. I then want to setup a branch policy for repo1, repo2, and repo3, setting this pipeline as a "Build Validation" so that it will trigger on Pull Requests and run the tests. I have tested this out and I'm not having much luck. It shows up in the PR, but shows as "not run" with a "Queue" button that doesn't seem to do anything. Here is the code: resources: repositories: - repository: repo1 type: git name: Project/repo1 trigger: - main - repository: repo2 type: git name: Project/repo2 trigger: - main - repository: repo3 type: git name: Project/repo3 trigger: - main name: $(date:yyyyMMdd)$(rev:.r) pool: name: Agent-Pool-1 steps: - checkout: self - checkout: repo1 - checkout: repo2 - checkout: repo3 - task: CmdLine@2 displayName: Run Tests inputs: script: echo running tests Is what I'm looking to do even possible? Or do I have to create 3 different pipelines for each repo to accomplish this? Thanks for the help!
Device In Azure AD showing as not compliant, yet in Intune the device is fine and compliant
Hello All I have several devices that are now failing SSO logins because of Conditional Access retuning as the device is not Compliant, Checking the device in Azure AD (Entra) is clearly shows the device is not compliant, which explains why the SSO logins are blocked. But when I check the device in Intune (Endpoint) it shows the device is compliant and all good (you will have to take my word the 2 screen shots are the same device as the host name is blurred) When checking the device ID in Azure AD and Intune they all match as you would expect. The Devices are checking in and Syncing with Azure and Intune on a regular basis. Azure is just not updating with the correct Compliance status from Intune. Any Ideas what is happening Cheers ColinOptimizing Azure DevOps Jira Integration: 5 Practical Use Cases for DevOps Teams
Many teams rely on Azure DevOps (ADO) for development and Jira for project or product management. While each tool is powerful on its own, things often get messy when work items, statuses, and updates live in separate systems. Integrating the two platforms can remove a lot of friction. Below are six common use cases I have seen from real teams, with concrete problems and solutions to make the connection between Jira and Azure DevOps work smoothly. 1. Keeping User Stories and Bugs in Sync Challenge: Teams use Jira for user requests and Azure DevOps for development tasks. Manually updating both systems is tedious and error-prone. Solution: Enable two-way synchronization so that changes in Jira automatically reflect in Azure DevOps and vice versa (including comments and status updates). This keeps bugs and stories aligned without duplicate work. “Before we integrated Jira with Aure DevOps, I spent too much time manually updating task statuses in both systems. Now, with the automatic sync, my team is focused on actual coding work instead of managing project statuses across platforms.” — DevOps Engineer 2. One-Way Sync for Project Management–First Teams Challenge: Some organizations plan and track everything in Jira but manage code exclusively in Azure DevOps. Developers only need the essentials pushed across. Solution: Use a one-way sync from Jira → Azure DevOps to bring over metadata like titles, statuses, sprints, and due dates. Developers see the context they need without cluttering both systems with manual updates. “We rely on Jira for all project planning and management, but the developers need a clean workspace in Azure DevOps. A one-way sync from Jira to ADO helps us keep things efficient and ensures developers always have the latest information without double entry.” — Product Owner 3. Creating Jira Tickets from Azure DevOps Tasks or Bugs Challenge: External partners or stakeholders may only work in Jira Service Management to manage tickets. Developers in Azure DevOps often need their work mirrored for transparency. Solution: Configure automated ticket creation in Jira when certain ADO tasks are tagged. Both teams can track progress in their preferred tool without duplicating effort. “We use Azure DevOps internally, but our external stakeholders only work in Jira. Automating the creation of Jira tickets based on Azure DevOps tasks or bugs has made collaboration seamless and ensured no work is lost in translation.” — DevOps Lead 4. Syncing Epics, Features, and Work Items Challenge: High-level epics might live in Jira, while features and tasks are managed in Azure DevOps. Without integration, visibility across systems is fragmented. Solution: Sync epics and features so Jira provides portfolio-level visibility, while Azure DevOps remains the system of record for detailed development work. This keeps roadmaps and execution aligned. “Tracking epics in Jira while managing the technical work in Azure DevOps used to cause us to lose visibility. Now, everything from high-level epics to individual tasks is in sync, so we always know where we stand.” — Azure DevOps Product Manager 5. Managing Multiple Jira Projects with One Azure DevOps Project Challenge: Large organizations often run multiple Jira projects (by teams or business units) but only one Azure DevOPs project for development. Syncing everything consistently is tough. Solution: Map multiple Jira projects to a single Azure DevOps project, syncing only the key data (titles, statuses, sprints, custom fields). This creates a unified development view without losing project-specific details. “We have multiple teams using different Jira projects, but we consolidate all development work into a single Azure DevOps project. Syncing across these platforms used to be a nightmare, but now everything stays aligned, and we’re able to track all initiatives in one place.” — Azure DevOps Engineer 💬 Have you integrated Jira with Azure DevOps in your team? What worked well, and what challenges did you run into?
Permission/access Audit in Powershell
Hello, im trying to generate a report on "who has access" on all Projects in Azure DevOps I use the following $organization = "RELEVENT NAME" $pat = "APATKEY" $baseUrl = "https://dev.azure.com/$organization/_apis" $APIVersion = "7.0" # Get all projects in the organization $projectsUrl = "$baseUrl/projects?api-version=$APIVersion" $projects = Invoke-RestMethod -Uri $projectsUrl -Method Get -Headers @{Authorization = "Basic $($pat)"} # Loop through each project and get the groups and permissions for each added user foreach ($project in $projects.value) { $projectName = $project.name $projectUrl = "$baseUrl/$projectName/_apis/graph/users?api-version=$APIVersion&direction=2&$top=5000" $addedUsers = Invoke-RestMethod -Uri $projectUrl -Method Get -Headers @{Authorization = "Basic $($pat)"} Write-Host "Project: $projectName" foreach ($user in $addedUsers.value) { $userId = $user.descriptor $userUrl = "$baseUrl/$projectName/_apis/accesscontrolentries?api-version=$APIVersion&identityDescriptor=$userId" $permissions = Invoke-RestMethod -Uri $userUrl -Method Get -Headers @{Authorization = "Basic $($pat)"} $groups = $user.memberOf | Where-Object { $_.subjectKind -eq "Group" } $groups = $groups | ForEach-Object { $_.displayName } $groups = $groups -join ', ' Write-Host "User: $($user.displayName), Groups: $groups" foreach ($permission in $permissions.value) { $permissionName = $permission.displayName Write-Host " Permission: $permissionName" } } Write-Host "" } can any one help me figure out why it returns empty all the time.
Import Test Steps via Excel Addin
Hello Together, we use the Excel AddIn (https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/office/bulk-add-modify-work-items-excel?view=azure-devops&tabs=agile-process In this Documentation you can find the following Information: "You can't import or update test case steps or other test artifacts" Actually you can, if you paste the Steps as XML Tags (https://oshamrai.wordpress.com/2019/03/01/azure-devops-services-rest-api-14-create-and-add-test-cases/ So far so good. It works pretty well. I define my TestStep in another Excel Sheet, transform these Steps into the XML Format via VBA Script and Paste it in the Excel Sheet for synchronisation. If i do so, with pasting the plain text directly in the Cell, it automaticly transform these to a text after publishing. In DevOps i got my Test Steps as defined. There is only one Problem: Otherwise, if I paste it not as Text but paste the cell, it stays as XML text after Publishing. The reason seems to be, that the PlugIn or DevOps converts the special Characters like < > " " into "<" """ etc. You only realize this, when you export these TestCases to csv. Thats why it will not detected as TestSteps. The "Paste special" options makes no different. In Case of Import a banch of Testcases via Excel i have to go into every cell an paste the XML String again. Is there any Workaround? (Using the grid view in Test Plans is no option for us) Greetings Mirco
'appcmd.exe' exited with code '1168' - release error
I'm trying to release my app on Azure DevOps but it is giving me this error on the "IIS Web App Manage" task: - Cannot find SITE object with identifier "SITE". 'appcmd.exe' exited with code '1168'. It is being released to 3 different servers ate the same time and in the other 2 servers it works. Since the last release I made, I didn't change anything in the server. I tried to restart the application pool, restart the server, and to release the old version of the application but it also failed.
Copy Config Db for Azure DevOps to new server?
I currently am migrating our DevOps server to a new location and I have decided to split the projects into different collections due to size and other reasons. My question is can I copy the configuration DB, change the URL and more to make this instance unique and have this running while the old DB is running? I primarily don't want to redo our entire server setup while making this as seemless as I can for our users. Thanks!
