# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand. overlay: 1.0.0 info: title: API Evangelist conversational phrasing for Microsoft Azure Microsoft.IoTOperationsMQ management… version: 1.0.0 extends: openapi/microsoft-azure-datalakeconnector-api-openapi.yml actions: - target: $.info update: x-apievangelist-phrasing: method: generated generated: '2026-09-26' generator: build-phrasing.py label: Generated by API Evangelist operations: 5 - target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTOperationsMQ/mq/{mqName}/dataLakeConnector'].get update: x-apievangelist-phrasing: intent: List Data Lake connectors on an MQ broker effect: read questions: - Which Data Lake connectors are configured on my IoT Operations MQ resource? - How do I see all data lake connectors attached to an MQ broker? instructions: - text: List Data Lake connectors on MQ resource {mq}. slots: mq: path.mqName - text: Show every data lake connector configured for {mq}. slots: mq: path.mqName method: generated generated: '2026-09-26' - target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTOperationsMQ/mq/{mqName}/dataLakeConnector/{dataLakeConnectorName}'].get update: x-apievangelist-phrasing: intent: Get a Data Lake connector effect: read questions: - How do I read the configuration of one Data Lake connector on IoT MQ? - What target and protocol does a specific data lake connector use? instructions: - text: Get Data Lake connector {connector} on MQ resource {mq}. slots: mq: path.mqName connector: path.dataLakeConnectorName - text: Show the settings of data lake connector {connector}. slots: connector: path.dataLakeConnectorName method: generated generated: '2026-09-26' - target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTOperationsMQ/mq/{mqName}/dataLakeConnector/{dataLakeConnectorName}'].put update: x-apievangelist-phrasing: intent: Create a Data Lake connector effect: write questions: - How do I set up a connector that sends MQTT data from IoT Operations to a data lake? - What extended location do I need when creating a Data Lake connector? instructions: - text: Create Data Lake connector {connector} on MQ resource {mq} in extended location {extendedLocation}. slots: connector: path.dataLakeConnectorName mq: path.mqName extendedLocation: requestBody.extendedLocation - text: Create data lake connector {connector} on {mq} with properties {properties}. slots: connector: path.dataLakeConnectorName mq: path.mqName properties: requestBody.properties method: generated generated: '2026-09-26' - target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTOperationsMQ/mq/{mqName}/dataLakeConnector/{dataLakeConnectorName}'].delete update: x-apievangelist-phrasing: intent: Delete a Data Lake connector effect: destructive questions: - How do I remove a Data Lake connector from an MQ broker? - Can I stop sending MQTT data to the lake by deleting the connector? instructions: - text: Delete Data Lake connector {connector} from MQ resource {mq}. slots: mq: path.mqName connector: path.dataLakeConnectorName - text: Remove data lake connector {connector}. slots: connector: path.dataLakeConnectorName method: generated generated: '2026-09-26' - target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.IoTOperationsMQ/mq/{mqName}/dataLakeConnector/{dataLakeConnectorName}'].patch update: x-apievangelist-phrasing: intent: Update a Data Lake connector effect: write questions: - Can I change the tags or properties on an existing Data Lake connector? - How do I patch a data lake connector that's already running? instructions: - text: Update tags on Data Lake connector {connector} of MQ {mq} to {tags}. slots: connector: path.dataLakeConnectorName mq: path.mqName tags: requestBody.tags - text: Patch existing data lake connector {connector} with properties {properties}. slots: connector: path.dataLakeConnectorName properties: requestBody.properties method: generated generated: '2026-09-26'