ADO New Repository Created Notification

Overview

ADO New Repository Created Notification is a scheduled polling flow that monitors Azure DevOps for newly created Git repositories and posts an alert to a Microsoft Teams channel. It uses a SharePoint tracking list to maintain state between runs, ensuring each new repo triggers exactly one notification. Designed for DevOps admins who need to track repository sprawl and enforce naming conventions across their ADO organization.

Use Case

Organizations with multiple development teams often see uncontrolled repository creation — repos with inconsistent naming, repos in the wrong project, or repos created without the team's awareness. This flow gives DevOps admins a passive monitoring system: every 4 hours it checks for repos that weren't there before and posts a structured Teams notification with repo name, project, default branch, and a direct link to the repo in ADO.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Change polling frequency

Edit the Recurrence trigger interval (default: every 4 hours). More frequent runs detect new repos faster but increase API calls against ADO and SharePoint.

Filter by project

Add a $filter (or project segment) to the ADO HttpRequest URI to limit results to specific projects: _apis/git/repositories?api-version=7.0&project={projectName}.

Add email notification

Insert a SendEmailV2 (Office 365 Outlook) action after the Teams post inside the Apply to Each loop to also email DevOps admins for each new repo.

Customize the Teams message

Edit the HTML in Post New Repo Alert to Teams to include naming-convention rules, compliance links, or @mentions of the DevOps owners.

Add naming convention validation

Insert a Condition after extracting repo details that checks item()?['name'] against a regex pattern, and only alert on non-compliant names.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

not(contains(body('Select_Known_Repo_IDs'), item()?['id']))

greater(length(body('Filter_New_Repositories')), 0)

coalesce(items('Apply_to_Each_New_Repository')?['defaultBranch'], 'Not set')

items('Apply_to_Each_New_Repository')?['webUrl']

utcNow()