GitHub Copilot Customization Explained for Beginners: Instructions, Prompt Files, Skills, Agents, and Hooks Introduction If you've recently started using GitHub Copilot, you've probably come across terms like Instructions , Prompt Files , Skills , Agents , and Hooks . At first glance, they all seem to do the same thing—they tell Copilot what to do. So why does GitHub have five different customization features? The answer is simple: each feature solves a different problem. Think of GitHub Copilot as a new developer joining your team. On their first day, you don't just hand them code. You explain your coding standards, give them reusable templates, teach them specialized knowledge, assign them a role, and automate repetitive tasks. That's exactly how GitHub Copilot customization works. In this article, you'll learn what each feature does, when to use it, and how they all work together. By the end, you'll know which feature to start with and which ones can wait un...
Setting up Azure Service Connection in Azure DevOps
You can specify your
Azure subscription directly in the release pipeline task, or you can use an
organizational account or a Service Principal and configure Service connection in Azure DevOps.
In this post will see how Service Principal can be created.
In this post will see how Service Principal can be created.
Tools which can be used
to create Service Principal in Azure:
- Using Azure PowerShell
- Using Azure Portal
- Using Azure CLI 2.0 Portal
Irrespective of the
tool choice commands remain same. There are two types of authentication available
for service principals: Password-based authentication, and certificate-based
authentication.This post we will be looking demonstrating Password-based authentication.
Steps
Steps
1. Log into Azure by running the below command.
When prompted, open the browser and login with Microsoft credentials.
az login
2. Create a Service Principal by running the
following command. The output displayed will be similar to the screenshot below.
az ad
sp create-for-rbac --name <http://AzureDevOps>
Note:
AppId and Password from this step which will be used in future steps
3. Role assignment for the Service Principal. The
output displayed will be similar to the screenshot below. Output should display
the role definition what we have provided.
az
role assignment create --assignee <AppId> --role Contributor
If you
are receiving null information back after running this command, you can also
check in the azure Portal by logging into your azure subscription and in the
Azure Portal going to Subscriptions > Access
control (IAM).
4. Log in with the Service Principal to verify if
the access is working fine by running the following command. Use the values
from Step 2 for AppId, Password and Tenant_ID.
az
login --service-principal --username <App_Id> --password <Password>
--tenant <TENANT_ID>
Popular posts from this blog
Tidy up - Unused Project and Nuget package reference using Visual Studio 2019
If you are a Developer/Architect using Visual Studio as IDE for your development activities, this blog post will be of your interest. During the Ignite 2021 conference, Microsoft released Visual Studio 2019 v16.9 and v16.10 Preview 1. As part of version 16.10 Preview 1, one of the cool features they introduced is to "Remove Unused References..." for any Projects and Nuget packages that are not in use. At the time of writing this blog post, we have Visual Studio Version 16.10.0 (official release) which includes this new feature. As part of development, we generally get carried away and introduce new Nuget package references to your project and add new references to your Projects. By the end of development, you will not be 100% sure which are not being referenced and unused which means you will leave those unused project references in your application. Now you might be wondering what's the big deal in it since it doesn't harm. The advantage of removing unused project r...
Azure Front Door vs Azure Traffic Manager?
In my previous blog post, we looked in detail Azure Front Door (AFD) . In this blog post, let's compare Azure Front Door (AFD) with another popular Azure service named Azure Traffic Manager (ATM). Prior to AFD most of the applications made use of ATM in their architecture now with AFD being available it's good to understand in which scenarios these individual services are ideal. Azure Front Door (AFD) Azure Front Door Service (AFD) a scalable and secure entry point for the fast delivery of your global applications. Azure Front Door allows you to transform your global (multi-region) applications into robust, high-performance applications, APIs, and content. Azure Traffic Manager (ATM) Azure Traffic Manager is a DNS-based traffic load balancer for geographically distributed Datacenters. Traffic Manager uses DNS to direct traffic to endpoint based on the traffic routing method and health of the endpoints. Similarities between AFD and ATM Both Azure Services support Multi-...
Authenticate Azure Functions - API Keys
In this blog post, we will see one of the ways to secure your Azure Functions using API keys. Security plays a key role as part of SDLC (Software Development Life Cycle) doesn't matter whether it's exposed to the client/public or even if it's internal. There are multiple ways to secure your Azure Functions like API Keys, Certificate, API Mgmt, App Service Authentication, etc. If you are new to the Cloud and Azure Functions but want to make a start with minimal effort and less setup of Infrastructure, then API Keys is the ideal choice. Azure Functions allows you to secure HTTP-triggered functions by API access key in the request. As part of creating new Azure Functions, we can select the Authorization Level enum value. If we set the Authorisation level to Anonymous, no security applied which means no authentication applied for the endpoint. Authorization Level - Function By setting the Authorisation level to Function each Azure Functions require a specific API key to Au...
Comments
Post a Comment