You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Migrate Microsoft.Azure.Management.DigitalTwins to Azure.ResourceManager.DigitalTwins #43
What would you like to be added:
Replace package Microsoft.Azure.Management.DigitalTwins with Azure.ResourceManager.DigitalTwins.
Migration guide: https://aka.ms/dotnet/t2/migration
This is a breaking change. The approved public api checked in ApiApprovalTests will need an update.
There is also a chance that System.Text.RegularExpressions 4.3.1 can be removed as a pinned transitive dependency due to this migration.
Replaced Microsoft.Azure.Management.DigitalTwins and the Fluent management SDK with Azure.ResourceManager.DigitalTwins 1.3.2.
Management authentication now uses Azure.Core.TokenCredential, including DefaultAzureCredential and ClientSecretCredential. The client ID/client secret/tenant ID registration remains available.
The new SDK does not expose the old provider operation-list API, so the liveness check now reads the configured Digital Twins Azure resource. Both AddAzureDigitalTwin overloads and the subscription health-check constructors require the full resourceId; the credential needs permission to read that resource, such as the Reader role. Resource IDs are validated to prevent probing the wrong resource type.
Removed the explicit System.Text.RegularExpressions pin. The restored dependency graphs for netstandard2.0, net8.0, and net10.0 contain none of the removed legacy SDK or regex packages.
Updated the public API approval snapshot, migration documentation, and offline HTTP tests for successful reads, 401/403/404 failures, cancellation, repeated probes, and multiple resource IDs.
Validation: solution-wide and source/test dotnet format --verify-no-changes --severity warn checks passed; the source builds for all three target frameworks; 39 tests passed on .NET 8 (including API approval) and 38 on .NET 10.
Activity
Migrate Azure Digital Twins health checks to the ARM SDK
maikebing commentedon Oct 3, 2026
Thanks for raising this. Implemented in 80fd11bb.
Microsoft.Azure.Management.DigitalTwinsand the Fluent management SDK withAzure.ResourceManager.DigitalTwins1.3.2.Azure.Core.TokenCredential, includingDefaultAzureCredentialandClientSecretCredential. The client ID/client secret/tenant ID registration remains available.AddAzureDigitalTwinoverloads and the subscription health-check constructors require the fullresourceId; the credential needs permission to read that resource, such as the Reader role. Resource IDs are validated to prevent probing the wrong resource type.System.Text.RegularExpressionspin. The restored dependency graphs fornetstandard2.0,net8.0, andnet10.0contain none of the removed legacy SDK or regex packages.Validation: solution-wide and source/test
dotnet format --verify-no-changes --severity warnchecks passed; the source builds for all three target frameworks; 39 tests passed on .NET 8 (including API approval) and 38 on .NET 10.All 84 CI workflows and both GitHub CodeQL checks passed on the final
mastercommit e9a14dd5. DigitalTwin CI · Code Scanning · Code Quality.The package README includes updated registration examples and migration notes.