Exploring GitHub Copilot

GitHub Copilot is a game-changer in the coding world. It’s like having a coding “genius” sitting right next to you, ready to help you at any time. Yeah, you read that right. It’s like having a very senior developer available for all your questions whenever you need them. And here's why I'm especially thrilled: As I get ready for an internal workshop on December 7th at our London office, I'm preparing a session about this very exciting topic. In the run-up to this event, I've been diving deep into GitHub Copilot's capabilities, and I’m happy to share my findings with you over this blog post.

If you want to learn more about GitHub Copilot, I recommend that you take the Microsoft learning path: “GitHub Copilot Fundamentals - Understand the AI pair programmer” that served as the primary source of content for this blog post.

What is GitHub Copilot?

In a nutshell, GitHub Copilot (going forward, Copilot) is a virtual, AI pair programmer that can help you write code faster and with less work. It works tirelessly by your side offering autocomplete-style suggestions on your code and comments. 

Research reveals that developers with access to Copilot finished their programming tasks 55.8% quicker than a control group without the AI pair programmer by their side. This demonstrates that Copilot increases developer productivity significantly and is an added value for those using it. For the full research, see The Impact of AI on Developer Productivity: Evidence from GitHub Copilot.

Copilot vs. ChatGPT

During my research, I considered whether ChatGPT can serve as an alternative to an AI pair programmer such as Copilot. At the end of the day, ChatGPT is free and user friendly, plus my colleagues might already be using it. Now, although ChatGPT is free and appealing, Copilot has more to offer for people who write code. To illustrate, I created the following comparison.

Feature	ChatGPT	GitHub Copilot Individual
Subscription cost	Free	$10/month
Primary function	Conversational AI	AI pair programmer
Availability	Web-based application, mobile app	IDEs (Integrated Development Environments)
Audience	General public, various industries	People who write code
Model	GPT-3.5, focused on natural language or code	Codex, a modified version of GPT-3, focused on code
Personal use	Yes, general usage	Yes, primarily for coding
Ease of use	User-friendly interface	Requires familiarity with IDEs
Learning and improvements	Pre-trained, continuous learning from interactions	Pre-trained, learns from code repositories and interactions

Copilot is based on the OpenAI Codex model, a programming model, that is focused on any type of programming tasks such as creating functions and fixing bugs. If you use the Copilot Chat to ask for support with preparing a dinner party, you will get the following answer: Sorry, but I can only assist with programming related questions. The focus of Copilot on programming tasks and the additional features it brings around that, makes it a strong peer to any person who writes code.

Now, if you don’t have access to Copilot, ChatGPT serves as an alternative, but it isn’t as specialized in programming tasks as Copilot.

Licenses

Copilot offers three licensing plans: Individual, Business, and Enterprise (release planned for February 2024). For more details on the different licenses and benefits, see GitHub Copilot pricing. This blog post focuses on the capabilities of the GitHub Copilot Individual plan.

How Copilot works

Copilot runs as a plugin within popular IDEs such as Visual Studio Code, Visual Studio, JetBrains, or Neovim. You can also use Copilot via GitHub Codespaces, a hosted developer environment that runs in the cloud.

When you type in your IDE, Copilot considers the context of the code already written, including comments, the filename, the file extension, and other open files in the IDE. This context goes through a proxy that filters out hate speech and personal data before it’s sent to Open AI. The AI model analyzes the context and generates code suggestions. These suggestions are displayed in the IDE in real-time, offering one or more alternatives for you to choose from. You can then modify, accept, or reject these suggestions. 

Your interaction helps Copilot provide more accurate suggestions over time as it adapts to your coding style. Copilot also uses your feedback on the suggestions to further improve the model. I’m not sure however whether this feedback loop also applies to Copilot for Business that has a major focus on data privacy.

Some practical tips 😉

During my hands-on trial with Copilot, I didn’t see the code block suggestions. A quick Ctrl + Enter (Windows) brings up the Copilot completions panel with many code suggestions. Also, you can accept a code suggestion using the Tab key (Windows). 

One special aspect that applies to Copilot, as described by Microsoft, is “Surround”. This means that Copilot uses the code you've already written—including comments, the filename, the file extension, and other open files in the IDE—to provide more tailored code suggestions. Consider opening more files in your IDE to provide extra context to Copilot.

Prompt engineering

You can't talk about successful generative AI interaction without talking about prompt engineering. The art of prompt engineering is crucial in reaching Copilot's full potential. A prompt is your instruction to the AI, and the more accurate and clear your prompts are, the better code suggestions Copilot generates. For example, using a comment like “// Create an API endpoint” isn't specific enough and can result in an output that doesn't meet your intentions. However, if you are more specific and define a clear scope, such as “// Create an API endpoint using the React framework that accepts a JSON payload in a POST request”, the output will more likely meet your expectations. Like anything in life, repeatedly practicing helps you get better, in this case, with prompt engineering. To learn more about prompt engineering, see Prompt Engineering Guide.

Summary

GitHub Copilot is more than a tool; it's the next level in programming and I wish Copilot had been there when I was an active developer. Its seamless integration into IDEs transforms it into the perfect programming “buddy” directly where you need it.

There might be many other features that I haven't explored, but I definitely loved these:

• Code suggestion: Suggestion of one or more code alternatives that you can accept, reject, or modify. The suggestions appear when you start to write code or by writing natural-language comments that describe your intent.
• GitHub Copilot Chat: A feature that makes difference, offering a conversational programming experience and responding to your questions with insights from your code's context and cursor position in the IDE. This helps you avoid context switching and navigating interruptions to look for support on the internet.
• Surround: Copilot’s ability to use additional information (the code already written, including comments, the filename, the file extension, and other open files in the IDE) around a comment or code as context for the response.

I look forward to finishing my slides for the upcoming workshop and soon having a great time with my colleagues as we discuss and apply Copilot.

See more

• https://docs.github.com/copilot/quickstart
• The previous image was generated using OpenAI's DALL·E.

Thanks for reading,

Jarbas

Integrate with Announcements in Viva Connections using the Microsoft Graph API

In the constantly evolving Microsoft 365 world, there's always something new to explore. One of the latest additions to catch our attention is the Announcements feature in Viva Connections. This feature introduces publishing capabilities to Viva Connections, enhancing communication within organizations by allowing communicators to share targeted, time-sensitive updates and information with their team members. In this post, I share with you my findings about how to extend Viva Connections Announcements using the Microsoft Graph API.

Anatomy of Announcements 

First things first, behind the scenes Announcements is not a common list in SharePoint, but a document library that can be accessed directly via Viva Connections or in SharePoint via the following URL: {SiteUrl}/_layouts/15/announcements.aspx. Communicators can use this area to create, manage, and share announcements to keep their team informed. Technically, an announcement is stored in XML format as an .aspx page.

Key properties for announcements:

• Audience Targeting: When creating an announcement, audience targeting is essential and mandatory. You can target up to 10 audiences, which can be Microsoft Entra ID security groups or Microsoft 365 groups. This ensures that your message reaches the right people.
• End date and time: Setting an end date and time for your announcement is mandatory. You can schedule it to remain visible for up to two weeks from the original publishing date.
• Message: The message is where you convey the details. Maximum of 250 characters.
• Title: Each announcement must have a title but keep it concise as you're limited to 60 characters.
• Schedule to send later: If timing is crucial, you can schedule your announcement to send later. Scheduling is available only in half-hour increments, so plan accordingly.

Accessing Announcements

The most recent announcement takes the spotlight in Viva Connections. The next four announcements are accessible through a carousel format. If you want to view all announcements, a "See all" button opens a modal dialog listing all announcements in descending order.

Extending Announcements 

Microsoft Viva Connections has had so far limited extensibility options, primarily related to Dashboard cards (aka. adaptive card extensions). However, the landscape is changing with the introduction of new Viva Connections features such as Announcements and Company Links. These features leverage the SharePoint infrastructure, opening the door to a wider range of integration scenarios. Now, you can integrate with SharePoint to enhance the Viva Connections experience.

Extending via the Microsoft Graph API

At the time of this written, Microsoft hasn’t introduced a dedicated API set to integrate with Announcements in Viva Connections. However, you can use the driveItem API to seamlessly integrate with the Announcements library in SharePoint. The following examples show the requests I used to create a new announcement in Viva Connections.

Downloading an announcement

I first ran a GET request to download an existing announcement from the Announcements library.

This is what the response object looks like:

Uploading an announcement

You can upload announcements in the form of .aspx pages to the Announcements library. For this example, I updated the XML content of the previous response before uploading the new announcement to the Announcements library.

The previous request creates a new announcement in the Announcements library; however, the announcement isn’t yet visible in Viva Connections. To ensure your announcement appears in Viva Connections, remember to publish the page. Note that you'll need to check out the .aspx page before you can proceed with checking it in and publishing it.

Checking out the .aspx page (announcement)

Checking in and publishing the .aspx page (announcement)

Exploring deeper with internal APIs

For those who enjoy taking a deeper look at internal APIs, I found an endpoint that returns announcements the signed-in user has dismissed.

https://example.sharepoint.com/sites/homesite/_api/EmployeeExperience/GetAnnouncementsState. 

The EmployeeExperience path in this endpoint already exists in Microsoft Graph. I’m curious whether Microsoft plans to extend the employeeExperience resource in the future to expose other Viva APIs publicly 🤔

API integration considerations

While Announcements in Viva Connections offer powerful communication capabilities, it's worth noting that Microsoft doesn't provide dedicated Viva Connections APIs for seamless integration. To work with Announcements, you have to rely on SharePoint operations. However, this approach can be risky, as Microsoft can change the structure of the Announcements library without prior notice. Announcements are saved in XML format on .aspx pages and relying on this XML structure can be challenging because Microsoft can alter it at any time. This represents a challenge for building production-ready integrations, especially considering the ever-changing landscape of Microsoft 365.

In conclusion, Announcements in Viva Connections are a valuable tool for enhancing communication within your organization. Communicators have an additional instrument with support for audience targeting that they can use to increase their reach. As a developer or ISV, understanding the extensibility options and the potential challenges can help you make the most of this feature and potentially extend Microsoft’s services.

See more

Use announcements in Viva Connections

Thanks for reading,

Jarbas

Attending the IntraTeam event Copenhagen 2023

I look forward to attending the IntraTeam event in Copenhagen on May 25th, 2023. IntraTeam is an industry conference focused on modern intranets, collaboration, and communication. The amazing lineup of speakers comprises of employee communication leaders, Microsoft employees, and software vendors. The agenda looks great and I'm especially curious about the following sessions:

• Viva Engage for communications and engagement by Dan Holme (Product leader, Viva Engage at Microsoft)
  Curious about: Understand how Viva Engage empowers leaders and employees to engage at scale, and how the results are measured
   
• The Digital Era: A new frontier for internal comms by Steffen Henke (Global Head of Internal Communications at Deutsch Post DHL - DPDHL)
  Curious about: Understand how DPDHL approaches employee communication with 600.000 employees
  
  
• Generative AI – what internal comms needs to know by David Bowman (Product Director at Fresh Intranet)
  Curious about: Understand how communicators can apply generative AI in employee communication

Let's get in touch if you're also going to participate in the event!!!

Event information in:

• Home page: https://event.intrateam.com/
• Schedule: https://event.intrateam.com/programme/
• Tickets: https://event.intrateam.com/tickets/

Copyright:
Event image source

Speaking at Staffbase VOICES 2023 Partners Pre-Day in Berlin

Staffbase VOICES is an employee comms event that brings together the employee communicators community and industry experts together to learn, network, and find joy in our shared work. On May 2^nd in a pre-day event for the Staffbase business partners, Felicia Flemming (Team Lead, Go-to-Market Strategy) and I (Group Product Manager) will talk to our partners about employee communication and how Staffbase and Microsoft come together to address this topic.

I look forward to speaking and networking with our partners, attending the VOICES event, and spending time with my colleagues and our customers.

Let's get in touch if you're also going to participate in this event!

See you soon 😉 

Graph API News: APIs for managing shared channels now available in Microsoft Graph

The roll out for the Microsoft Teams Connect shared channels has already started, making thousands of customers very happy. As a software vendor who builds a governance and provisioning solution for Microsoft 365, I am not only interested in the feature roll out but also in the API support for it so I can extend my product accordingly. Today, I want to share with you that the APIs for managing shared channels are available in Microsoft Graph as a beta release. In this blog post, I won’t go through the benefits of shared channels because this has already been presented by other authors (for example, Microsoft Teams Connect shared channels is rolling out to public preview); rather, I will focus on the newly introduced APIs.

Important: Currently, the Microsoft Graph API to create a shared channel is only available to a limited audience. This means that many customers cannot create shared channels programmatically and have to use the Microsoft Teams client for that. For now, only the Microsoft Graph APIs to manage shared channels are available!

Actually, I was a bit surprised by this statement, but I trust that the corresponding team at Microsoft has a good reason for that. In general, I was really looking forward to the API to create shared channels so I can use it in my provisioning and governance solution. I think for now, we just need to wait for the release of this API, which will happen hopefully soon.

Anyway, the APIs for managing shared channels are available, which is already a very good start for governance-related scenarios. I created the following structure that helps me to better understand the use cases where the new shared channel APIs can be used:

Maintain shared channels in user-related scenarios 

• List teams that a user is associated with
• List the users allowed to access a shared channel
• Check whether a user has access to a shared channel

Maintain scenarios when a team hosts one or more shared channel

• List teams shared with a channel
• Get a team shared with a channel
• Unshare a channel with a team

Maintain scenarios when teams have associated shared channels 

• List all channels in a team (either in the team or shared with the team)
• List only channels shared with a team
• Remove a shared channel from a team

I look forward to Microsoft to also release the API to create shared channels for all customers. For now, my team and I will give the new shared channels APIs a try so we can learn and understand them better 😁

Thanks for reading,
Jarbas

Graph API News: API to list all Microsoft Teams in a tenant is now available

So far, to list all Microsoft Teams teams in an organization programmatically, you had to work with the groups API. I believe that the preferred approach has been to filter all groups by the resourceProvisioningOptions property to get only those groups that have teams. The following is an example of this request:

GET /groups?$filter=resourceProvisioningOptions/Any(x:x eq 'Team')

However, this request returns a response that is partially helpful. On the one hand, it returns all groups that have teams. On the other hand, additional requests are needed to return team specific properties, such as isArchived, specialization, and webUrl.

The Microsoft Graph Teams team has just introduced a new BETA API that allows users to list all teams in a tenant:

GET /teams

The not-so-good part of this implementation is the limited number of properties (id, displayName, and description) that a call to GET /teams return. Basically, it gives you less data than working with the groups API that, for example, also returns the group/team’s visibility. Nevertheless, progress is progress 😀 and I appreciate the invest. In general, I hope the list of supported properties returned from a GET /teams call will increase rapidly. This would help developers to reduce the number of additional requests to retrieve all teams related properties and consequently improve applications. 

The following example shows the response of a GET/teams request. You will notice that the response body also contains a set of other properties that are returned with null, which represents a behavior similar to a call to GET/joinedTeams.

{
   "@odata.context":"https://graph.microsoft.com/beta/$metadata#teams",
   "value":[
     {
         "id":"b4f36c5f-c66e-4212-9b87-8817dabd8230",
         "createdDateTime":null,
         "displayName":"Project Alpha",
         "description":"All about the Project Alpha.",
         "internalId":null,
         "classification":null,
         "specialization":null,
         "visibility":null,
         "webUrl":null,
         "isArchived":null,
         "isMembershipLimitedToOwners":null,
         "memberSettings":null,
         "guestSettings":null,
         "messagingSettings":null,
         "funSettings":null,
         "discoverySettings":null
     },
     {
         "id":"78ee08a5-6c7d-4136-b2ca-78b049738f96",
         "createdDateTime":null,
         "displayName":"Project Alice",
         "description":"All about the Program Alice.",
         "internalId":null,
         "classification":null,
         "specialization":null,
         "visibility":null,
         "webUrl":null,
         "isArchived":null,
         "isMembershipLimitedToOwners":null,
         "memberSettings":null,
         "guestSettings":null,
         "messagingSettings":null,
         "funSettings":null,
         "discoverySettings":null
     }
   ]
}

For more details on this API, see List teams.

Keep in mind that the use of Microsoft Graph BETA APIs for production applications is not supported because BETA APIs are subject to change. I am crossing my fingers that this specific API will indeed change, for example, all teams related properties will be returned with proper values 😊

Thanks for reading,
Jarbas Horst

Upgrade from classic authentication experience in Azure Functions

The classic Authentication / Authorization experience in Azure Function apps will be removed from the Microsoft Azure portal in December 2021. As a result of a lack of Microsoft documentation, we don't know currently what side effects this change will bring to the way how authentication will be handled for Azure Function apps that remain in the old model. To avoid potential issues, I've followed the Microsoft instructions and upgraded to the new authentication experience. For more details, see how to configure your Azure Function app to use Azure Active Directory login. 

The following steps describe how I upgraded from the classic authentication experience in a secured Azure Function app:

1. Go to the Azure portal > Your secured Azure Function app  > Authentication

2. If the Authentication page shows a warning indicating that the classic Authentication experience will be removed and it includes an Upgrade button, it means that the classic Authentication experience is still in use:

However, if you experience an UI that is different than the one demonstrated in the previous image, the Azure Function app already uses the new experience and no further actions are required.

3. To upgrade to the new Authentication experience, click on the Upgrade button. Now, read the instructions carefully and click again on Upgrade:

4. Wait for the upgrade to complete, which might take a few seconds.

5. After the upgrade to the new Authentication experience has finished, you will see an UI that is similar to the one demonstrated in the following image:

The upgrade process is done if you have followed all the previous steps.

Thanks for reading,

Jarbas