Skip to content

Commit a44a1d0

Browse files
authored
Merge pull request #288187 from veyalla/patch-4
clarify fabric steps
2 parents c47272c + 6e79c47 commit a44a1d0

File tree

2 files changed

+8
-1
lines changed

2 files changed

+8
-1
lines changed

articles/iot-operations/connect-to-cloud/howto-configure-fabric-endpoint.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ To send data to Microsoft Fabric OneLake in Azure IoT Operations Preview, you ca
2424
- **Microsoft Fabric OneLake**. See the following steps to create a workspace and lakehouse.
2525
- [Create a workspace](/fabric/get-started/create-workspaces). The default *my workspace* isn't supported.
2626
- [Create a lakehouse](/fabric/onelake/create-lakehouse-onelake).
27+
- If shown, ensure *Lakehouse schemas (Public Preview)* is **unchecked**.
28+
- Make note of the workspace and lakehouse names.
2729

2830
## Create a Microsoft Fabric OneLake dataflow endpoint
2931

@@ -228,11 +230,16 @@ For more information about dataflow destination settings, see [Create a dataflow
228230

229231
The following authentication methods are available for Microsoft Fabric OneLake dataflow endpoints. For more information about enabling secure settings by configuring an Azure Key Vault and enabling workload identities, see [Enable secure settings in Azure IoT Operations Preview deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
230232

233+
Before you create the dataflow endpoint, assign workspace *Contributor* role to the IoT Operations extension that grants permission to write to the Fabric lakehouse.
234+
235+
![Screenshot of IoT Operations extension name to grant workspace access to.](media/howto-configure-fabric-endpoint/extension-name.png)
236+
237+
To learn more, see [Give access to a workspace](/fabric/get-started/give-access-workspaces).
238+
231239
#### System-assigned managed identity
232240

233241
Using the system-assigned managed identity is the recommended authentication method for Azure IoT Operations. Azure IoT Operations creates the managed identity automatically and assigns it to the Azure Arc-enabled Kubernetes cluster. It eliminates the need for secret management and allows for seamless authentication with Azure Data Explorer.
234242

235-
Before you create the dataflow endpoint, assign a role to the managed identity that grants permission to write to the Fabric lakehouse. To learn more, see [Give access to a workspace](/fabric/get-started/give-access-workspaces).
236243

237244
# [Kubernetes](#tab/kubernetes)
238245

306 KB
Loading

0 commit comments

Comments
 (0)