Upgrade to Azure.Connectors.Sdk 0.9.0-preview.1

[daviburg]

Summary

Upgrades from Microsoft.Azure.Connectors.Sdk 0.8.0-preview.1 to Azure.Connectors.Sdk 0.9.0-preview.1 (release notes).

Breaking Changes Addressed

Change	Before	After
Package ID	Microsoft.Azure.Connectors.Sdk	Azure.Connectors.Sdk
Namespaces	Microsoft.Azure.Connectors.DirectClient.*	Azure.Connectors.Sdk.* + .Models
Client names	SharepointonlineClient	SharePointOnlineClient (PascalCase)
Constructors	new XxxClient(url, managedIdentityClientId)	new XxxClient(url, credential)
Exceptions	Office365ConnectorException.StatusCode	ConnectorException.Status
IsFatal()	SDK-internal ExceptionExtensions.IsFatal()	Local ExceptionExtensions.cs helper restores the guard
AzureLogAnalytics	Removed	Replaced by AzureMonitorLogs

New Capabilities Demonstrated

• DI extension methods — Program.cs reduced from ~150 lines to ~30 lines using AddOffice365Client(), AddTeamsClient(), etc.
• DefaultAzureCredential via DI — single registration used by all connector clients for local dev (Development environment only)
• ARM connector — newly added with ArmFunctions.cs (4 endpoints)
• Unified ConnectorException — inherits RequestFailedException, all connectors use the same exception type

Validation

• Build succeeds against published NuGet package Azure.Connectors.Sdk 0.9.0-preview.1
• End-to-end tested locally against BTS4 gateway connections (Office365, Teams, OneDrive, MS Graph, Office365Users, AzureBlob)

[Copilot]

Pull request overview

This pull request upgrades the DirectConnector sample to Azure.Connectors.Sdk 0.9.0-preview.1, updating namespaces/client names, switching to the new DI registration extensions, and aligning error handling with the unified ConnectorException.

Changes:

• Bump the SDK package reference to Azure.Connectors.Sdk 0.9.0-preview.1 and update namespaces/models across all connector samples.
• Simplify Program.cs by registering connector clients via services.Add*Client(...) extension methods and registering a shared TokenCredential.
• Replace connector-specific exceptions with ConnectorException and migrate from StatusCode to Status in error handling.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 9 comments.

Show a summary per file

File	Description
DirectConnector/SmtpFunctions.cs	Switch SMTP client/models to Azure.Connectors.Sdk and update exception handling.
DirectConnector/Program.cs	Replace manual client factories with SDK DI extension methods and shared TokenCredential.
DirectConnector/OneDriveFunctions.cs	Update OneDrive client/models and exception handling to the new SDK.
DirectConnector/Office365UsersFunctions.cs	Update Office365 Users client/models and exception handling to the new SDK.
DirectConnector/MsGraphFunctions.cs	Update MS Graph client/models and exception handling to the new SDK.
DirectConnector/MqFunctions.cs	Update MQ client/models and exception handling to the new SDK.
DirectConnector/local.settings.json.template	Replace Azure Log Analytics config keys with Azure Monitor Logs and add ARM config keys.
DirectConnector/DirectConnector.csproj	Swap package reference to Azure.Connectors.Sdk 0.9.0-preview.1.
DirectConnector/ConnectorTriggerMetadataAttribute.cs	Update documentation references to the new SDK namespaces.
DirectConnector/ConnectorFunctions.cs	Update Office365/SharePoint/Teams clients/models and exception handling to the new SDK.
DirectConnector/AzureLogAnalyticsFunctions.cs	Migrate to Azure Monitor Logs client/models and update operations/exception handling.
DirectConnector/AzureBlobFunctions.cs	Update Azure Blob client/models and exception handling to the new SDK.

Comments suppressed due to low confidence (1)

DirectConnector/ConnectorFunctions.cs:175

• Catching all exceptions and converting them into an HTTP 500 response can inadvertently swallow fatal process-level exceptions (OOM, StackOverflow, etc.). Consider reintroducing a fatal-exception filter (e.g., catch (Exception ex) when (!IsFatal(ex))) or rethrowing known-fatal exceptions so the host can terminate appropriately.

        catch (Exception ex)
        {
            this._logger.LogError(ex, "Error in SendEmail.");

            var errorResponse = request.CreateResponse(HttpStatusCode.InternalServerError);

[Copilot]

Pull request overview

Copilot reviewed 15 out of 15 changed files in this pull request and generated 11 comments.

[Copilot]

Pull request overview

Copilot reviewed 15 out of 15 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 15 out of 15 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 15 out of 15 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 15 out of 15 changed files in this pull request and generated no new comments.