Pinned Posts
Forum Widgets
Latest Discussions
How to structure product development work items
Hi, we are currently starting to develop a product, that consists of hardware and software development. All parts are closely interconnected with each other. I have to capture the customer requirements, create a design and architecture. Then implement it, test it, document it and so on. There may come additional requirements in the future, but these will be only minor changes. All in all it is very clear at this point. Now I have created a new azure devops project with the CMMI template. Is CMMI a good template or should I use a different one? In my understanding I only create one epic, where everything I create will be linked to. My customer requirement will be created as features. My own requirements will be created as requirement work item types. Where do I add the design and architecture work results? Do I have to create a new custom work item type that gets linked to my own requirements? I hope someone can point me in the right direction and I will not start with a completely wrong project structure. Thank you very much. Best regards, SebastiansebastianmichelMay 23, 2025Copper Contributor582Views0likes1CommentUnable to register agents in Deployment Group even with Administrator access
Hi Team, We are facing an issue with respect to deployment groups in Azure DevOps. Except the creator of the deployment group, No one else is able to register targets to the deployment despite having administrator access granted. Here is an example scenario: User A created deployment group DG1 and then added the "Project Administrators" and "Deployment Group Administrators" as adminstrators to DG1. But none of the members from above groups are able to register targets to the deployment group DG1. only user A is able to register the target to the DG1. Error: You do not have permissions to register targets. Looks like the security settings in the Deployment groups are not having any affect on the actual permissions related to the Deployment group. Please look into this issue. Let me know if you need any additional information related to this.Bhanu_reddyMay 23, 2025Copper Contributor1KViews0likes1Comment๐ Strengthening Azure DNS Zone Security with RBAC and Resource Locks
๐ DNS security is more than just configuration itโs about protecting critical assets against unauthorized changes and accidental deletions. ๐ Managing DNS zones effectively requires a layered security approach. ๐ Two powerful mechanisms in Azure : Role-Based Access Control (RBAC) and Resource Locks ๐ Role-Based Access Control (RBAC) ๐ * Granular DNS Access Control * RBAC ensures controlled access management at both the DNS zone and record set levels. * Instead of assigning broad permissions, RBAC enables precise delegation using built-in roles such as: ๐น Owner โ Full control over the DNS zone, including configurations and deletions. ๐น Contributor โ Can modify DNS settings but cannot change access permissions. ๐น Network Contributor โ Can manage networking configurations related to DNS, but not modify records. ๐น DNS Zone Contributor โ Dedicated role for managing DNS zones without broader networking privileges. โ Key Advantages of RBAC in DNS Security: โ Prevent unauthorized modifications by restricting access to only necessary roles. โ Ensure operational integrity by limiting exposure to critical configurations. โ Improve governance by aligning roles with organizational security policies. ๐ Resource Locks ๐ * Guardrails for DNS Protection * Even with well-defined RBAC settings, accidental deletions can still occur. * Azure Resource Locks add an additional safeguard by preventing changes to a DNS zone or specific record sets. ๐น Zone Lock ----> Protects an entire DNS zone from being deleted, preserving all associated record sets. ๐น SOA Lock ----> Prevents unintentional zone deletions while allowing record modifications within the zone. โ How Resource Locks Enhance Security: โ Shields DNS zones from accidental or malicious deletions. โ Maintains continuity by ensuring record sets remain intact. โ Strengthens compliance controls for critical infrastructure. ๐ Best Practices for Securing DNS with RBAC & Resource Locks ๐ธ Assign least privilege rolesโnever give unnecessary access. ๐ธ Implement locks on essential zones to prevent configuration errors. ๐ธ Regularly audit access permissions using Azure Policy & Activity Logs. ๐ธ Use Automation & Alerts to track modifications for enhanced security. ๐น Implementing RBAC & Resource Locks ensures your cloud environment remains secure, operational, and fault-tolerant.Mahmoud_Yaseen_AZHeroMay 22, 2025Copper Contributor15Views0likes0Commentsdynamic pipeline and deployments with approvals
I am looking to create a multistage YAML pipeline in Azure DevOPS that: * Dynamically generates jobs based on the value(s) of a variable from a previous step (e.g., host names). * Ensures that each dynamically created job includes its own approval step, either through ManualApproval@0 or via an environment. The challenge I am facing is that while "strategy: matrix" allows for the dynamic creation of build jobs, this strategy is not permitted for deployments, which are necessary for implementing approval steps. Do you have any suggestions on how to resolve this issue?BigUnixAdmin007May 22, 2025Copper Contributor12Views0likes1CommentCannot RDP to azure VM from local domain joined PC
I have an Azure VM behind an Azure VPN that I cannot connect to from certain PCs. This is an azure government instance at the free tier. The VM only has a Private IP, and can only be accessed when connected to the VPN. The VM doesn't have a DNS name/FQDN. I looked into giving it one, but the instructions call for a public IP so I couldn't complete the process. I am using the private IP address of the VM, and an Entra ID credential to connect through RDP I can reach the VM from my laptop, which is azure AD joined to a different tenant. I can reach the VM from a non-domain joined PC from the network I am working in. I CANNOT reach the VM from a local domain joined PC on the same network, even before applying policies. I get a "user logon failed" message from the PC I don't see the logon attempts in Entra ID Admin Center under "Sign-in Logs" I'm all out of things I know to try to get this to work. Any insight or guiding questions would be greatly appreciated. Thank you!iandoyle345May 21, 2025Copper Contributor36Views0likes3CommentsAzure VM Networking Components Real Case Scenario
๐ Public IP ๐ ๐น Public IPs allow internet-based services to reach Azure resources, such as web applications hosted on VMs or Azure App Services. ๐น Azure resources can use Public IPs to communicate with external services, ensuring connectivity for APIs, databases, and other cloud-based applications. ๐น Public IPs can be assigned as static (fixed address) or dynamic (changes over time). Static IPs are ideal for services requiring a consistent address, while dynamic IPs are useful for temporary workloads. ๐ Azure Load Balancer (External / Internal) ๐ ๐น Distributes Internet Traffic โ Balances incoming requests from the internet across multiple backend resources. ๐น Balances Private Network Traffic โ Distributes requests within an Azure Virtual Network (VNet). ๐น Supports Multi-Tier Architectures โ Ideal for backend services like databases and application layers. ๐น Enhances Availability โ Ensures high availability by routing traffic to healthy instances. ๐น Provides Outbound Connectivity โ Enables Azure VMs to communicate with external services using NAT. ๐ VNET Subnets Segmentation ๐ ๐น Web Subnet โ Contains two VMs, each with a Network Interface Card (NIC) and is protected by a Network Security Group (NSG) to filter traffic based on rules. ๐น App Subnet โ Similar to the Web Subnet, hosting two VMs with NICs and NSGs, but uses an internal load balancer to balance traffic within the subnet. ๐น Data Subnet โ Also includes two VMs with NICs and NSGs, leveraging an internal load balancer for optimized traffic management. ๐น Gateway Subnet โ Hosts the VPN Gateway, ensuring connectivity between on-premises networks and Azure. ๐ Azure Network Security Groups (NSGs)๐ ๐น Traffic Filtering โ NSGs allow or deny inbound and outbound traffic based on defined security rules. ๐น Granular Control โ Rules can be applied at the subnet or network interface level for precise traffic management. ๐น Default Security Rules โ Azure provides built-in rules to ensure basic security, which can be overridden with custom rules. ๐น Priority-Based Processing โ Rules are evaluated in order of priority (100-4096), with lower numbers processed first. ๐น Supports Service Tags โ Simplifies rule management by using predefined tags like Internet, VirtualNetwork, and AzureLoadBalancer. ๐ Azure VPN Gateway ๐ ๐น Secure Connectivity โ Establishes encrypted connections between Azure Virtual Networks (VNets) and on-premises networks. ๐น Site-to-Site VPN โ Enables secure communication between an on-premises network and Azure using IPsec/IKE VPN tunnels. ๐น Point-to-Site VPN โ Allows individual devices to securely connect to Azure from remote locations using OpenVPN, IKEv2, or SSTP. ๐น VNet-to-VNet Connectivity โ Facilitates secure communication between multiple Azure VNets. ๐น ExpressRoute Failover โ Provides a backup connection for ExpressRoute in case of failure. ๐น High Availability โ Supports active-active configurations for redundancy and reliability. If you found this valuable, consider sharing so more professionals can benefit. Let's keep the conversation growing! ๐Mahmoud_Yaseen_AZHeroMay 21, 2025Copper Contributor17Views0likes0Comments๐ฅ Hybrid Networking 101: Linking On-Prem to Azure ๐ฅ
Many organizations seek to extend their networks to include subnets and virtual machines (VMs) hosted on Azure. The goal is to enable seamless connectivity between on-premises computers in a data center and Azure-based virtual machines. ๐น Common Use Cases for Hybrid Networking: # Application Connectivity: You have an Azure-hosted application that needs access to your on-premises database servers. # Branch Office Integration: Your business operates retail stores worldwide and requires a single centralized service to connect all locations. # Remote Access: You need secure remote access to your Azure VMs and applications. # Data Synchronization: You want to connect on-premises servers with Azure servers for real-time synchronization and data transfer. # To address these scenarios, Azure provides four key networking solutions: โ Point-to-Site VPN (P2S) โ Site-to-Site VPN (S2S) โ ExpressRoute โ Azure Virtual WAN One essential component that supports all these solutions is Azure VPN Gateway. Let's explore its capabilities! ๐ ๐ Azure VPN Gateway ๐ # Secure Connectivity Between Azure & On-Premises by encrypting data while transferring it between Azure VNets and on-premises servers over the internet. # Multiple connections can be established using a single VPN Gateway, sharing available bandwidth across all VPN tunnels. # The gateway consists of Azure-managed VMs, automatically deployed and configured in a GatewaySubnet with a CIDR size of /27. # There are two types of gateways: ๐น VPN Gateway (for encrypted connections) ๐น ExpressRoute Gateway (for dedicated high-speed connectivity) ๐ก Gateway SKUs define performance characteristics, including: # Supported tunnel types (S2S, P2S, VNet-to-VNet) # Maximum aggregate throughput # BGP (Border Gateway Protocol) support # Scalability options (resize within the same generation and family via Azure Portal or PowerShell) ๐ VPN Gateway Types: # Route-Based VPN: Supports S2S & P2S connectionsโwidely used in hybrid networking. # Policy-Based VPN: Limited to Basic SKUs and allows only S2S connections (not ideal for Remote Access). ๐น Local Network Gateway: Represents your on-premises router or firewall, enabling Azure to recognize your internal network's public IP and subnets for connectivity via IPSec IKEv1/2. ๐น Azure Availability Zones can be leveraged for high availability and service continuity. ๐ Point-to-Site VPN (P2S) ๐ ๐น Secure access for individual users connecting remotely to Azure VNets. ๐น Supported protocols: OpenVPNยฎ (SSL/TLS-based; compatible with Windows, Mac, Linux, Android, iOS) SSTP (TLS-based; Windows-only) IKEv2 (IPsec VPN solution; Mac-supported) ๐น Authentication Methods: (1) Certificate Authentication (requires client certificates issued from a trusted root certificate). (2) Azure AD Authentication (available for OpenVPN clients). (3) Active Directory Domain Server Authentication (via RADIUS server integration). ๐ Site-to-Site VPN (S2S) ๐ ๐น Enables on-premises data centers to connect with Azure VNets via IPSec IKEv1/2. ๐น Supports VNet-to-VNet connections over Microsoft's backbone network. ๐น Compatible with hardware devices from vendors such as Cisco, Fortinet, Barracuda, Check Point. ๐น Supports software VPN devices, including Microsoft RRAS and Linux Openswan. ๐น Enables dynamic routing via BGP to propagate network changes automatically. ๐ ExpressRoute ๐ ๐น Dedicated high-speed connectivity to Microsoft Cloud (Azure, Microsoft 365). ๐น Up to 100 Gbps speeds with low latency, ideal for business-critical applications. ๐น Layer 3 connectivity, using BGP for seamless route exchange between on-premises and Azure networks. ๐ Azure Virtual WAN ๐ ๐น A scalable networking service integrating VPN, ExpressRoute, and SD-WAN solutions. ๐น Provides branch connectivity using site-to-site VPN or private ExpressRoute connections. ๐น Supports remote user VPN (P2S) for secure external access. ๐น Follows hub-and-spoke architecture, ensuring full mesh connectivity across Azure regions. If you found this valuable, consider sharing so more professionals can benefit. Let's keep the conversation growing! ๐Mahmoud_Yaseen_AZHeroMay 20, 2025Copper Contributor54Views0likes0Comments๐ฅThe Power of Azureโs Security Arsenal ๐ฅ
โ Using a Public IP without securing your Azure applications and resources exposes you to security threats. Today, weโll explore the most powerful security solutions from Azureโs arsenal. โ Azure provides a multi-layered approach (more than one layer of protection) to secure your resources when using a Public IP. Organizations can now transform this open gateway into a fortified checkpoint. Hereโs how these tools work together to mitigate risks: ๐ Azure DDoS Protection ๐ โ Protects your resources and services from being overwhelmed by malicious traffic. This excellent service is available for Network & IP Protection SKUs. โ Uses Machine Learning to distinguish between normal traffic patterns and malicious flooding attempts (such as SYN floods or UDP amplification attacks) before they impact your applications and services ensuring availability. ๐ Azure Web Application Firewall (WAF) ๐ โ Adds application-layer protection, intercepting HTTP/HTTPS traffic for inspection. โ Blocks suspicious attacks like SQL injection or XSS by applying OWASP core rule sets, which define how attacks occur and how to defend against them, with continuous updates. โ Enhances security for customer-facing services, ensuring trust and protection for your website and users. ๐ Network Security Groups (NSGs) ๐ โ Acts as a virtual firewall at the subnet or network interface level, filtering traffic based on predefined rules. โ Can allow only trusted HTTPS (port 443) connections while blocking unsolicited RDP or SSH attempts. โ Implements the critical security principle of reducing attack surface, ensuring only authorized traffic reaches your target resources. ๐ Azure Private Link ๐ โ In some scenarios, avoiding Public IPs altogether is the best security approach. This powerful service allows secure access to Azure SQL Database or Storage via Private Endpoints inside your virtual network. โ Helps organizations minimize external exposure while maintaining secure, private connections to necessary services. ๐ Azure Bastion ๐ โ Provides secure access to Azure VMs without Public IPs, using RDP/SSH over encrypted TLS 1.2 traffic. โ Uses a browser-based HTML5 web client to establish RDP/SSH sessions over TLS on port 443, fully compatible with any firewall. โ Connects to VMs via Private IPs while enforcing NSG rules to allow access only through Azure Bastion. If you found this valuable, consider sharing so more professionals can benefit. Let's keep the conversation growing! ๐Mahmoud_Yaseen_AZHeroMay 20, 2025Copper Contributor18Views0likes0Comments๐ Mastering Azure Management with Global Admin Elevation ๐
โ Microsoft Entra ID and Azure resources are secured independently from one another. โ Microsoft Entra role assignments do not grant access to Azure resources. โ Azure role assignments do not grant access to Microsoft Entra ID. โ As a Global Administrator in Microsoft Entra ID, you can assign yourself access to all Azure subscriptions and management groups in your tenant. โ Use this capability if you don't have access to Azureโฏsubscription resources, such as virtual machines or storage accounts, andโฏyouโฏwant to use your Global Administrator privilege to gain access to those resources. โ When you elevate your access, you are assigned the User Access Administrator role in Azure at root scope (/).โฏThis allows you to view all resources and assign access in any subscription or management group in the tenant. โ User Access Administrator role assignments can be removed using Azure PowerShell, Azure CLI, or the REST API. ๐ Why would you need to elevate your access? If you are a Global Administrator, there might be times when you want to do the following actions: โ Regain access to an Azure subscription or management group when a user has lost access โ Grant another user or yourself access to an Azure subscription or management group โ See all Azure subscriptions or management groups in an organization โ Allow an automation app (such as an invoicing or auditing app) to access all Azure subscriptions or management groups # Perform steps at root scope # Follow these steps to elevate access for a Global Administrator using the Azure portal. (1) Sign in to the Azure portal as a Global Administrator. Note : If you are using Microsoft Entra Privileged Identity Management, activate your Global Administrator role assignment !! (2) Browse to Microsoft Entra ID > Manage > Properties. (3) Under Access management for Azure resources, set the toggle to Yes. (4) Select Save to save your setting. If you found this valuable, consider sharing so more professionals can benefit. Let's keep the conversation growing! ๐Mahmoud_Yaseen_AZHeroMay 20, 2025Copper Contributor39Views0likes0CommentsBranch is not created by az repos ref create command
I want to automate branch creation for my project. I am using the command az repos ref create --name testrelease/$MAJ_VER.$MIN_VER.$PATCH_VER --object-id xxxxxxxxxxxxxxxxxxxxxxxx --org https://dev.azure.com/myorg/ --project myproj--repository myrepo I see the response, 2023-11-30T16:00:57.5538690Z { 2023-11-30T16:00:57.5539015Z "customMessage": null, 2023-11-30T16:00:57.5539286Z "isLocked": false, 2023-11-30T16:00:57.5539489Z "name": "refs/testrelease/0.3.0", 2023-11-30T16:00:57.5539871Z "newObjectId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", 2023-11-30T16:00:57.5540718Z "oldObjectId": "0000000000000000000000000000000000000000", 2023-11-30T16:00:57.5541098Z "rejectedBy": null, 2023-11-30T16:00:57.5541701Z "repositoryId": "123212312321321312312312312321312312321", 2023-11-30T16:00:57.5542107Z "success": true, 2023-11-30T16:00:57.5542284Z "updateStatus": "succeeded" 2023-11-30T16:00:57.5545083Z } 2023-11-30T16:00:57.6145902Z ##[section]Finishing: create a branch But I couldnt find the branch created in azure devops.Latha1595May 20, 2025Copper Contributor519Views0likes1Comment
Resources
Tags
- azure2,265 Topics
- Azure DevOps1,390 Topics
- Data & Storage379 Topics
- Networking235 Topics
- Azure Friday222 Topics
- App Services200 Topics
- blockchain168 Topics
- devops162 Topics
- Security & Compliance148 Topics
- analytics134 Topics