[Workaround & Headache Prevention] Successfully create teams channel notification subscription with Microsoft Graph .NET Client Library v5

When upgrading from Microsoft Graph .NET Client Library v4 to v5, adapting GraphServiceClient methods for team channel notification subscriptions according to official documentation caused issues. Despite the recommended code changes, they did not work as expected. After extensive debugging and research, a workaround was found to resolve the issue. This is a known issue with POST requests in v5.

[HOWTO] Prevent self-hosted Azure DevOps agents from running out of disk space

The Azure DevOps pipeline, running on a self-hosted agent, failed due to insufficient disk space. Investigation revealed old directories consuming space. Enabling the maintenance job feature can automate cleaning to prevent such issues. It's advisable to schedule maintenance during low agent activity to avoid disruption. For detailed maintenance job information, refer to documentation.

[HOWTO] Automate release notes generation with an Azure DevOps YAML pipeline

This blog post demonstrates how to create a YAML pipeline in Azure DevOps for generating release notes for each production release, listing solved work items. The process involves preconditions, the Generate Release Notes (Crossplatform) extension, and the implementation of the release notes YAML pipeline. The post also covers importing the pipeline in Azure DevOps and local testing.

[HOWTO] Exclude content from GitHub Copilot

GitHub announced the re-deployment of content exclusions, allowing repo administrators and organization owners to manage content exclusion settings for GitHub Copilot. It's in beta for Copilot Business subscribers and supported in various IDEs. Exclusions can be set for specific files, files in any Git-based repo, or a whole repo.

[HOWTO] Suggest changes directly in Azure DevOps pull requests

Azure DevOps allows proposing changes directly in pull requests, simplifying the process of suggesting small alterations like translations or formatting. Users can mark the part needing a change, click the Comment icon, select the Insert a suggestion icon, and edit the content. The pull request author can then accept and apply the suggested change directly in Azure DevOps.

[NoBrainer] Solve AuthorizationPermissionMismatch error on terraform init

The error "Failed to get existing workspaces: containers.Client#ListBlobs: Failure responding to request: StatusCode=403" in Terraform with an Azure backend indicates a permission issue. To resolve this, assign the Storage Blob Data Contributor or Owner role to the user or service principal. After assignment, use 'az logout' and 'az login -t [tenant id]' commands to refresh the token.

Website Powered by WordPress.com.

Up ↑