Forum Discussion

rbcvl's avatar
rbcvl
New Member
18 days ago

Azure Artifact Feed - Connection string not supported

Hi everyone,

I'm trying to create a new Azure Artifact Feed (Preview) connection in Microsoft Fabric, but I'm consistently getting the following error:

Unable to create connection for the following reason:
Connection string is not supported.

Details:
Query contains unsupported function. Function name: AzureArtifactFeed.Contents

Environment

  • Microsoft Fabric
  • Connection Type: Azure Artifact Feed (Preview)
  • PyPi Feed URL format: https://pkgs.dev.azure.com/<organization>/_packaging/<feed>/...
  • Creating the connection from Manage Connections and Gateways > New Connection > Cloud

Questions

  1. Has anyone successfully configured an Azure Artifact Feed connection in Fabric recently?
  2. Could this be related to the note displayed in the UI indicating that some cloud connections are not supported by Dataflows Gen1 and Datamarts?

Any insights or confirmation that this is a known issue would be greatly appreciated.

Thanks!

4 Replies

  • v-abhinavmu's avatar
    v-abhinavmu
    Community Support

    Hi rbcvl​,

    Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to ShivekMaharaj​ for sharing valuable insights.

    Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

    Thank you for being part of the Microsoft Fabric Community.

    • rbcvl's avatar
      rbcvl
      New Member

      Hi,

      We're still investigating this case with the help of Microsoft's support team.

      • v-abhinavmu's avatar
        v-abhinavmu
        Community Support

        Hi rbcvl​,

        Thank you for the update.

        We’re glad to hear that you’re working with Microsoft Support to investigate the issue. Please feel free to share any findings or updates from the support team here if they become available, as they may be helpful to other community members experiencing a similar issue.

        Thank you for keeping us updated.

  • ShivekMaharaj's avatar
    ShivekMaharaj
    Power Participant

    Hi rbcvl​,

    I don't think the generic Dataflows Gen1/Datamarts note is the explanation here.

    Microsoft's current Fabric Environment library documentation explicitly tells you to create an Azure Artifact Feed (Preview) connection through Settings > Manage connections and gateways > New > Cloud, so you're using the documented connection path.

    It also documents both project-scoped and organization-scoped Azure Artifact feeds as supported. For authentication, the supported paths are a PAT with Packaging: Read plus Feed Reader access, or Workspace Identity. The connection should also have Allow Code-First Artifacts like Notebooks to access this connection enabled.

    One limitation I'd rule out is workspace networking. Microsoft currently says Azure Artifact Feed libraries aren't supported in workspaces with Private Link or Outbound Access Protection enabled.

    If those prerequisites are all satisfied, the interesting part of your error is:

    Query contains unsupported function. Function name: AzureArtifactFeed.Contents

    Given that Microsoft explicitly documents creating this connection through the same UI, I would read that more as the Preview connector failing during connection validation than as an unsupported connection-string format. That's an inference though, not a confirmed known issue.

    I'd also verify the feed URL directly from Azure DevOps Connect to feed > pip. Azure DevOps supports both project-scoped and organization-scoped PyPI feed URLs.

    I couldn't find a currently published Fabric known issue for this exact error. If the URL/auth/networking checks are clean and AzureArtifactFeed.Contents is still rejected during creation, I'd raise it with Microsoft Support and include the screenshot, tenant/region, authentication method, workspace networking configuration and the exact feed scope.

    AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.