Conversation
This was
linked to
issues
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix for Issue #480
Root cause:
Get-AzDataFactoryV2Dataset(and otherGet-AzDataFactoryV2*cmdlets) throw "Unable to deserialize the response" when the ADF service contains objects whose types aren't supported by the installed Az.DataFactory module version. This blocksDeleteNotInSourceentirely.Three files changed/created:
private/AdfPSObjects.class.ps1(new)Six lightweight wrapper classes (
AdfPSDataset,AdfPSDataFlow,AdfPSPipeline,AdfPSLinkedService,AdfPSIntegrationRuntime,AdfPSTrigger) following the existingAdfPS<SimplifiedType>naming convention.Get-SimplifiedTypealready strips theAdfPSprefix, so these integrate withRemove-AdfObject's type switch without any changes there.private/Get-AdfObjectsFromServiceRestAPI.ps1(new)A fallback function that lists ADF objects of any given type via the management REST API — same approach already used for credentials via
Get-AzDFV2Credential. Returns the appropriate typed wrappers above.public/Get-AdfFromService.ps1(modified)Each
Get-AzDataFactoryV2*call is now wrapped in atry-catch. On failure it logs a warning and falls back to the REST API. The happy path (no deserialization issues) is completely unchanged.