--assign-identity VS. --mi-system-assigned

[rafaarcangel]

The page said we needed to use '--assign-identity' when working with system-managed identity... but I received a warning on pipelines that said:

WARNING: Argument 'assign_identity' has been deprecated and will be removed in a future release. Use '--mi-system-assigned' instead.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 19f647d0-36be-3633-03fa-eb5ad31169aa
• Version Independent ID: 7476c99b-5867-2a21-62ed-8bd94e2b2b57
• Content: az dt
• Content Source: latest/docs-ref-autogen/dt.yml
• GitHub Login: @rloutlaw
• Microsoft Alias: routlaw

[yonzhan]

@wangzelin007 for awareness

[wangzelin007]

Hi @rafaarcangel, Can you try az dt create --dt-name ${{parameters.instanceName}} --resource-group ${{parameters.resourceGroup}} --location ${{parameters.region}} --mi-system-assigned? Can you explain what exactly you mean by the page? It would be even better if you can send the complete pipeline execution log. You can click View raw log on the top right and copy the full log.

[rafaarcangel]

My pipeline runs successfully, with both commands. But there is a warning to change to 'new' my-system-assigned'.

This it's only a comment to update the documents you have on Microsoft, with the latest info:

• https://learn.microsoft.com/en-us/azure/digital-twins/how-to-set-up-instance-cli -> section System-assigned identity command

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-iot-cli-triage.

Issue Details

---

The page said we needed to use '--assign-identity' when working with system-managed identity... but I received a warning on pipelines that said: WARNING: Argument 'assign_identity' has been deprecated and will be removed in a future release. Use '--mi-system-assigned' instead.   --- #### Document Details ⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.* * ID: 19f647d0-36be-3633-03fa-eb5ad31169aa * Version Independent ID: 7476c99b-5867-2a21-62ed-8bd94e2b2b57 * Content: [az dt](https://learn.microsoft.com/en-us/cli/azure/dt?view=azure-cli-latest) * Content Source: [latest/docs-ref-autogen/dt.yml](https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/latest/docs-ref-autogen/dt.yml) * GitHub Login: @rloutlaw * Microsoft Alias: **routlaw**

Author:	rafaarcangel
Assignees:	wangzelin007
Labels:	`Service Attention`, `question`, `CI`, `IoT/CLI`, `Azure CLI Team`
Milestone:	Backlog

[wangzelin007]

@Azure/azure-iot-cli-triage, Maybe you should update your documentation to keep it up to date.

[wangzelin007]

Hi @rafaarcangel, Thanks for your feedback, it has been routed to the azure-iot team.

[baanders]

Hi! I'm the author of the Azure Digital Twins document you mentioned above.

I've confirmed the parameter should be updated from --assign-identity to --mi-system-assigned, and made the update to this document (and in a few other spots) in this pull request: https://github.com/MicrosoftDocs/azure-docs-pr/pull/221769

This should resolve this issue. Thank you for helping us keep our docs up to date! :)

[vilit1]

Closing issue as the doc has been updated for a while. If there are any other questions, feel free to create another issue