How to connect to the Self hosted mongoDB from Fabric.

Question

How to connect to the Self hosted mongoDB from Fabric.

Rajuvardhana K V 60

I tried to integrate the self hosted MongoDB to fabric but im getting the error

Connection to MongoDB server is timeout.

A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Selectors = MongoDB.Driver.MongoClient+AreSessionsSupportedServerSelector, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00.0150000 }, OperationsCountServerSelector }. Client view of cluster state is { ClusterId : "1", Type : "Unknown", State : "Disconnected", Servers : [{ ServerId: "{ ClusterId : 1, EndPoint : "10.6.0.6:27017" }", EndPoint: "10.6.0.6:27017", ReasonChanged: "Heartbeat", State: "Disconnected", ServerVersion: , TopologyVersion: , Type: "Unknown", HeartbeatException: "MongoDB.Driver.MongoConnectionException: An exception occurred while opening a connection to the server. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.

at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation)

at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)

at MongoDB.Driver.Core.Connections.SslStreamFactory.CreateStream(EndPoint endPoint, CancellationToken cancellationToken)

at MongoDB.Driver.Core.Connections.BinaryConnection.OpenHelper(CancellationToken cancellationToken)

--- End of inner exception stack trace ---

at MongoDB.Driver.Core.Connections.BinaryConnection.OpenHelper(CancellationToken cancellationToken)

at MongoDB.Driver.Core.Connections.BinaryConnection.Open(CancellationToken cancellationToken)

at MongoDB.Driver.Core.Servers.ServerMonitor.InitializeConnection(CancellationToken cancellationToken)

at MongoDB.Driver.Core.Servers.ServerMonitor.Heartbeat(CancellationToken cancellationToken)", LastHeartbeatTimestamp: "2026-01-09T06:40:09.7412433Z", LastUpdateTimestamp: "2026-01-09T06:40:09.7412433Z" }] }.

Activity ID: 05b51939-ba6c-471e-8a17-0b541569b176"

Shubhansh Saraswat 0 Reputation points

2026-03-12T07:29:44.6066667+00:00

@Rajuvardhana K V Did you get any solution to it ?

Johan Forssell 0

According to the supportedConnectionTypes API, the MongoDBForPipeline should accept NotEncrypted connections, but in reality it does not.

❯ curl -s \
  -H "Authorization: Bearer $AZTOKEN" \
  "https://api.fabric.microsoft.com/v1/connections/supportedConnectionTypes?gatewayId=<SOME-ID>" \
  | jq '.value[] | select(.type=="MongoDBForPipeline")'
{
  "type": "MongoDBForPipeline",
  "creationMethods": [
    {
      "name": "MongoDBForPipeline.Contents",
      "parameters": [
        {
          "name": "server",
          "dataType": "Text",
          "required": true,
          "allowedValues": null
        }
      ]
    }
  ],
  "supportedCredentialTypes": [
    "Basic"
  ],
  "supportedConnectionEncryptionTypes": [
    "NotEncrypted"
  ],
  "supportsSkipTestConnection": true,
  "supportedCredentialTypesForUsageInUserControlledCode": null
}

The interesting bit: "supportedConnectionEncryptionTypes": ["NotEncrypted"]. The connector advertises that it supports NotEncrypted, which I verified by PATCHing one of my connections, successfully.
But the underlying driver clearly ignores that setting and goes through SslStreamFactory anyway. That's a Fabric bug.
Where can I one report such a bug?

1 answer

Your answer

Shubhansh Saraswat 0 Reputation points

2026-03-12T07:29:44.6066667+00:00

@Rajuvardhana K V Did you get any solution to it ?
Johan Forssell 0 Reputation points

2026-05-28T10:19:31.4633333+00:00

According to the supportedConnectionTypes API, the MongoDBForPipeline should accept NotEncrypted connections, but in reality it does not.

❯ curl -s \ -H "Authorization: Bearer $AZTOKEN" \ "https://api.fabric.microsoft.com/v1/connections/supportedConnectionTypes?gatewayId=<SOME-ID>" \ | jq '.value[] | select(.type=="MongoDBForPipeline")' { "type": "MongoDBForPipeline", "creationMethods": [ { "name": "MongoDBForPipeline.Contents", "parameters": [ { "name": "server", "dataType": "Text", "required": true, "allowedValues": null } ] } ], "supportedCredentialTypes": [ "Basic" ], "supportedConnectionEncryptionTypes": [ "NotEncrypted" ], "supportsSkipTestConnection": true, "supportedCredentialTypesForUsageInUserControlledCode": null }

The interesting bit: "supportedConnectionEncryptionTypes": ["NotEncrypted"]. The connector advertises that it supports NotEncrypted, which I verified by PATCHing one of my connections, successfully.
But the underlying driver clearly ignores that setting and goes through SslStreamFactory anyway. That's a Fabric bug.
Where can I one report such a bug?

Answer 1

Manoj Kumar Boyini 19,595 Moderator

Hi Rajuvardhana K V

Kindly share this query in the Microsoft Fabric Community, where the Fabric product team and community experts can help you further:
https://community.fabric.microsoft.com/

0 comments