Share via

Authentication type is null in oracle linked service.

Mani 45 Reputation points
2025-11-26T21:05:03.6666667+00:00

Hi, I created the Oracle linked service in my feature branch and merged it into the main branch. The Git pipeline then published these changes to Data Factory live mode. The Oracle linked service was deployed to live mode, but the authentication type is showing as null. I had set the authentication type to Basic when I created the linked service in the feature branch. Is there a way to resolve this issue?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. VRISHABHANATH PATIL 1,725 Reputation points Microsoft External Staff Moderator
    2025-11-28T08:10:10.81+00:00

    Hi @Mani,

    Thank you for contacting Microsoft Q&A. Please find below the detailed steps to address the reported issue.

    This looks like a known/ongoing issue with Azure Data Factory (ADF) — specifically when deploying an Oracle 2.0 connector linked service via a Git-based CI/CD pipeline: the "authenticationType": "Basic" property doesn’t always get preserved publishing mode after publish, ending up as null. TECHCOMMUNITY.MICROSOFT.COM+1

    Root cause (known issue / bug)

    • The problem seems to stem not from your creation of the linked service, but from how ADF’s Git-publish (CI/CD) flow handles the Oracle connector JSON: during the publish step, the authenticationType property is dropped/omitted.
    • Multiple community reports and a fix announcement by Microsoft in May 2025 suggest that this is a bug in the Oracle connector (v2.0) that affected regions.
    • As a result, although in your feature branch (Git) the JSON shows "authenticationType": "Basic", after publishing the live-mode representation shows it as null. This causes authentication failures at runtime.

    What you should do now: work around / fix

    • Update to latest ADF version / ensure fix is applied
      • Verify whether your ADF workspace is in a region where the May 27, 2025, fix has been rolled out. The fix reportedly resolved the issue for Oracle 2.0 connector in affected regions.
      • If not updated yet, consider opening a support ticket with Microsoft to request the fix or migration of your workspace to a region that has the patched connector.
    • Manually patch the linked-service JSON in the published (live) workspace
      • In the ADF portal (live mode), locate the deployed Oracle linked service.
      • Edit its JSON definition and manually add:
      • "authenticationType": "Basic"

    (alongside the existing properties like server, username, password, connectVia, etc.)

    Save/publish the change to ensure ADF will honor the Basic auth setting at runtime.

      • This is effective (per community reports) when the automated publish dropped the authentication property.
    • If using scripted/automated deployments (e.g. PowerShell, ARM templates, Terraform), verify they include authenticationType
      • For example, some users reported that az datafactory linked-service create or Terraform-based deployment ignores the authentication property, leading to missing auth type after deployment.
      • If your CI/CD uses PowerShell, ARM, or Terraform, update the deployment definition to explicitly include "authenticationType": "Basic" (or parameterize it), rather than relying on default or omitted values.
    • Use secrets / Key Vault rather than embedding credentials directly
      • As a best practice (and partly to avoid secrets in Git), store database credentials (username/password) in an Azure Key Vault and reference them in the linked service. This doesn’t directly solve the authenticationType bug — but reduces risk and avoids “secrets in code” issues. This aligns with general ADF recommendations.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.