Skip to content

Instantly share code, notes, and snippets.

View jsquire's full-sized avatar

Jesse Squire jsquire

View GitHub Profile
@jsquire
jsquire / dotnet-sample-service-bus-batch-delete.md
Last active March 14, 2024 21:10
Service Bus: Batch Delete

Service Bus: Batch Delete

Currently, when messages are sent to Service Bus, they can only be removed by reading/completing them or waiting for them to age-out based on the retention policy. This can often become troublesome for applications that accumulate messages in their dead-letter queue when they do not wish to process them, or for applications with messages that are not actionable after a certain age.

Historically, developers have had to write code that loops to perform destructive reads for the messages that they want to remove. While this is relatively straightforward for purge scenarios, it can be tricky to do correctly when the desire is only to remove messages older than a given point in time.

To make this scenario easier for developers, Service Bus is adding a new operation capable of deleting batches of messages and limiting them to a specific time.

Goals

@jsquire
jsquire / example-sb-amqp.md
Created April 5, 2024 19:42
Example: Service Bus AMQP operations

Connections

Create connection

  • Use AMQP version 1.0.0.0

  • Use SASL with "MSSBCBS" as the mechanism name

  • Authorize via CBS to a dedicated link named "$cbs"

@jsquire
jsquire / event-grid-amqp-concept.md
Last active April 11, 2024 21:09
Event Grid: AMQP (early concept)

Event Grid: AMQP (early concept)

Things to know before reading

  • The names used in this document are intended for illustration only. Some names are not ideal and will need to be refined during discussions.

  • Some details not related to the high-level concept are not illustrated; the scope of this is limited to the high level shape and paradigms for the feature area.

  • Fake methods are used to illustrate "something needs to happen, but the details are unimportant." As a general rule, if an operation is not directly related to one of the Event Grid types, it can likely be assumed that it is for illustration only. These methods will most often use ellipses for the parameter list, in order to help differentiate them.

@jsquire
jsquire / concept-microsoft.messaging.md
Last active April 26, 2024 19:41
Microsoft Messaging: AMQP client library (early concept)

Microsoft Messaging: AMQP client library (early concept)

The high-level goal for the Microsoft Messaging client library is to provides a unified experience for core messaging scenarios needed by developers wishing to interact with Microsoft Fabric, Azure Event Grid, Azure Service Bus, and Azure Event Hubs.

Things to know before reading

  • The names used in this document are intended for illustration only. Some names are not ideal and will need to be refined during discussions.

  • Some details not related to the high-level messaging operations are not illustrated; the scope of this is limited to the high level shape and paradigms for the feature area.

@jsquire
jsquire / ai-triage.md
Created March 21, 2025 23:04
Leveraging AI-driven support automation for the Azure SDK repositories

Leveraging AI-driven support automation for the Azure SDK repositories

Executive summary

The Azure SDK GitHub repository experiences recurring support challenges, notably repetitive customer inquiries and inconsistent responsiveness across internal teams. Users submit issues already addressed in documentation or previously resolved issues, contributing to longer response times and unnecessary workloads. Additionally, engagement levels vary significantly among the teams responsible for different Azure SDK packages, leading to uneven customer experiences.

We propose implementing AI-driven support automation to streamline issue management and improve customer satisfaction. This solution will reduce time-to-resolution, deliver a consistent support experience, and enable engineering teams to focus on high-impact development efforts. Other key benefits include:

  • Improved automated triage classification of incoming GitHub issues.
  • Detection and intelligent response to common, previously solved questions.