undefined

Hi NTolani,

The connection you created in Manage connections and gateways is a service-side connection. Power BI Desktop does not automatically expose those connections in its Get Data window, so its absence there is expected.

The next step depends on which Azure Cosmos DB for MongoDB deployment you are using.

The hostname and account-key authentication in your example appear to be from the RU-based Azure Cosmos DB for MongoDB API, rather than MongoDB vCore. Microsoft’s current Azure Cosmos DB for MongoDB vCore Power Query connector is specifically for vCore clusters and supports both Power BI Desktop and Power Query Online. It would therefore not be the correct connector for an RU-based account.

For the RU-based MongoDB API, I would use the connection you already created with a Fabric pipeline or Copy job to load the required collections into a Lakehouse or Warehouse. Microsoft lists the Azure Cosmos DB for MongoDB connector in Fabric Data Factory as supporting Copy activity and Copy job through cloud, on-premises, or virtual network connectivity. You can then build the Power BI semantic model over the Lakehouse or Warehouse.

I would not use the Microsoft Cosmos DB ODBC driver for this account. Microsoft’s ODBC driver documentation states that it supports Azure Cosmos DB for NoSQL only, not the MongoDB API.

So the practical architecture would be:

Azure Cosmos DB for MongoDB → Fabric pipeline or Copy job → Lakehouse/Warehouse → Power BI

The account name and key you already have can be used as the MongoDB username and password where the Fabric connector requests basic authentication. Microsoft also recommends copying the complete MongoDB connection information from the Azure portal’s Connection strings page rather than manually constructing it.

I hope this helps clarify why the gateway connection is not appearing in Desktop. The key first step is confirming whether the account is MongoDB vCore or the RU-based MongoDB API, because the supported Power BI path differs between them.