@AndriyDmytrenko Thank you for asking this question. I will investigate and add this Feature! Thank you very much!

I realize this is an older feature request but this would be very useful for our team as well. We have a large inventory of M-series VMs that have Write Accelerator enabled which we'll be managing with Ansible. Our workaround right now is using a custom execution environment with the AZ CLI installed then using "az vm update -g <rg_name> -n <vm_name> --write-accelerator <disk_lun_num>=true" via the Command module. What takes about 15-20 lines of YAML could be cut down to 1 by adding this option.

Hi, is there any progress in this case? This issue/request is open since 2021 and since 2023 marked as high_priority.

By the way, it would go hand in hand with changes to the _info Module as well, as it shows "None" for attach_caching when Write Accelerator is enabled.

Seems like the "issue" starts deeper, as the azure.mgmt.compute (which is used by Ansible) is lacking it as well:

class CachingTypes(str, Enum, metaclass=CaseInsensitiveEnumMeta):
    """Specifies the caching requirements. Possible values are: **None,** **ReadOnly,** **ReadWrite.**
    The default values are: **None for Standard storage. ReadOnly for Premium storage**.
    """

    NONE = "None"
    READ_ONLY = "ReadOnly"
    READ_WRITE = "ReadWrite"

So the Python SDK for Azure doesn't offer a solution for this issue.
Created an issue on the Azure SDK for Python Repo:
Azure/azure-sdk-for-python#39243

@AndriyDmytrenko @unkaputtbar112 I am very sorry for missing this problem, I will add this function as soon as possible, thank you!

@AndriyDmytrenko @unkaputtbar112 I added parameter 'write_accelerator_enabled' in #1808, you can try it out, thank you!

@Fred-sun added my tests/feedback to the #1808
Thanks for your work :)