Azure Identity Usage Sample

Summary

The Event Hub client library will provide a new API surface for track two, which differs from that of the current track one version. To help illustrate usage of the new API for the target scenarios, a set of small, approachable, and self-contained sample projects is needed.

Scope of Work

• Implement a sample demonstrating a basic approach for creating an EventHubClient using an Azure identity as the credential and read basic metadata from the Event Hub to illustrate the client working.

• The sample should offer discussion and illustration of any needed Azure resources or configuration, such as creating a service principal and configuring RBAC on the Event Hub instance.

Out of Scope

• Creation of samples which illustrate other scenarios; these will be covered under a dedicated work item.

Success Criteria

• The sample has been created for the scenario, with a clear and simple approach and generous comments to support the goal of helping those unfamiliar with Event Hubs to get started in using it.

• The sample adheres to the coding conventions and standards defined for track two libraries.

• All projects in the solution compile; any warnings that exist have either been fixed or additional work items filed to address them if they were deemed non-critical.

[albertodenatale]

Apologies for the churn, and I appreciate your willingness to iterate. Truth be told, we’re thinking through the details together on this; I didn’t have a fully-baked plan going in (… and probably still don’t.)

With this task, I am as much committed as your are in providing Microsoft with something that fits the high standards that it sets for itself and I love iterations 😃

[jsquire]

I noticed the launchSettings.json is not in the .gitignore wonder if you want me to do anything with this?

I wouldn’t do that here, as it will bubble to the entire repository and is something that our engineering team owns. I’ll take a note and propose a change so that we don’t bog down with another 5+ people pulled into the review as code owners for that file.