Repository: ansible/ansible
Pull request: add note for Azure Availbility Zone
##### SUMMARY
add note to distribute Azure VMs in Availability Zones

Fixes #66149

##### ISSUE TYPE
Docs Pull Request

##### COMPONENT NAME
Microsoft Azure Guide


Problem statement:
How to distribute Azure VMs in Availability Zones
<!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->

##### SUMMARY
The current 'Microsoft Azure Guide' content is not enough for us to place Azure VMs in the **availability zones**. So I suggest adding some notes to this guide.

##### ISSUE TYPE
- Documentation Report

##### COMPONENT NAME
Microsoft Azure Guide(docs/docsite/rst/scenario_guides/guide_azure.rst)

##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below

```

##### CONFIGURATION
```paste below
$ ansible --version
ansible 2.9.2
  config file = None
  configured module search path = ['/Users/mitsuru/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/mitsuru/.local/share/virtualenvs/hive-builder-bq6LUPdg/lib/python3.7/site-packages/ansible
  executable location = /Users/mitsuru/.local/share/virtualenvs/hive-builder-bq6LUPdg/bin/ansible
  python version = 3.7.3 (default, Jun  7 2019, 11:23:14) [Clang 10.0.1 (clang-1001.0.46.4)]

```

##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->
Mac OS catalina 10.15.2

##### ADDITIONAL INFORMATION
When I tried to place VMs in the availability zones, I struggled with the following:

- OS disk and data disk must be a 'Managed Disk',  not 'Unmanaged Disk',  to place VM in the availability zones.
- When creating a VM with the azure_rm_virtualmachine, you need to specify explicitly managed_disk_type to change OS disk to 'Managed Disk'. Otherwise, 'os disk' becomes 'Unmanaged disk'.
- When creating a data disk with azure_rm_manageddisk, you need to specify explicitly storage_account_type to make it a 'Managed Disk'. Otherwise, the data disk will be 'Unmanaged disk'.
- 'Managed Disk' does not require 'Storage Account' or 'Storage Container' unlike 'Unmanaged Disk'. 
In particular, note that once a VM is created on an 'Unmanaged disk', an unnecessary 'Storage container' named "vhds" is automatically created.
- When creating an IP address with azure_rm_publicipaddress, it is necessary to specify 'standard' in the 'sku' property. Otherwise, the IP address cannot be used in the availability zones.

Hints from issue discussion:
Files identified in the description:
None

If these files are inaccurate, please update the `component name` section of the description or use the `!component` bot command.

[click here for bot help](https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md)
<!--- boilerplate: components_banner --->
cc @Fred-sun
@mit0223 Thank you for taking the time to report this issue! You mean we need to add how to differentiate Azure VM in Availability zones in the guide_azure.rst documentation. right?
@Fred-sun  Yes, I post this, thinking that I should add a description of the various difficulties that only arise when trying to place a VM in an availability zone.
@mit0223 Thank you for sharing this question. You are welcome to submit a PR repair question. Thank you very much!
@Fred-sun Now, it will be the same as ADDITIONAL INFORMATION in this issue, I will create a PR.
@mit0223 Thank you very much!

Commit message: Change title

Patch to review:
diff --git a/docs/docsite/rst/scenario_guides/guide_azure.rst b/docs/docsite/rst/scenario_guides/guide_azure.rst
index ff30aeaa3165a9..4b390c84353845 100644
--- a/docs/docsite/rst/scenario_guides/guide_azure.rst
+++ b/docs/docsite/rst/scenario_guides/guide_azure.rst
@@ -257,6 +257,31 @@ virtual network already with an existing subnet, you can run the following to cr
         version: latest
 
 
+Creating a Virtual Machine in Availability Zones
+..................................................
+
+If you want to create a Virtual Machines in Availability Zones,
+Note the following:
+
+* Both OS disk and data disk must be a 'Managed Disk', not 'Unmanaged Disk',
+  to create a Virtual Machine in Availability Zones.
+* When creating a Virtual Machine with the azure_rm_virtualmachine,
+  you need to specify explicitly managed_disk_type
+  to change OS disk to 'Managed Disk'.
+  Otherwise, OS disk becomes 'Unmanaged disk'.
+* When creating a data disk with azure_rm_manageddisk,
+  you need to specify explicitly storage_account_type
+  to make it a 'Managed Disk'.
+  Otherwise, the data disk will be 'Unmanaged disk'.
+* 'Managed Disk' does not require 'Storage Account' or 'Storage Container'
+  unlike 'Unmanaged Disk'.
+  In particular, note that once a Virtual Machine is created on an 'Unmanaged disk',
+  an unnecessary 'Storage container' named "vhds" is automatically created.
+* When creating an IP address with azure_rm_publicipaddress,
+  it is necessary to specify 'standard' in the 'sku' property.
+  Otherwise, the IP address cannot be used in Availability Zones.
+
+
 Dynamic Inventory Script
 ------------------------
 


Code review comments:
diff_hunk: @@ -257,6 +257,31 @@ virtual network already with an existing subnet, you can run the following to cr
         version: latest
 
 
+Creating a Virtual Machine in Availability Zones
+..................................................
+
+If you want to create a Virtual Machines in Availability Zones,
+Note the following:
+
+* Both OS disk and data disk must be a 'Managed Disk', not 'Unmanaged Disk',
+  to create a Virtual Machine in Availability Zones.
+* When creating a Virtual Machine with the azure_rm_virtualmachine,
+  you need to specify explicitly managed_disk_type
+  to change OS disk to 'Managed Disk'.
+  Otherwise, OS disk becomes 'Unmanaged disk'.
+* When creating a data disk with azure_rm_manageddisk,
+  you need to specify explicitly storage_account_type
+  to make it a 'Managed Disk'.
+  Otherwise, the data disk will be 'Unmanaged disk'.
+* 'Managed Disk' does not require 'Storage Account' or 'Storage Container'
+  unlike 'Unmanaged Disk'.
path: docs/docsite/rst/scenario_guides/guide_azure.rst
text: @user1:
```suggestion
  unlike  a n unmanaged disk.
```

diff_hunk: @@ -257,6 +257,31 @@ virtual network already with an existing subnet, you can run the following to cr
         version: latest
 
 
+Creating a Virtual Machine in Availability Zones
+..................................................
+
+If you want to create a Virtual Machines in Availability Zones,
+Note the following:
+
+* Both OS disk and data disk must be a 'Managed Disk', not 'Unmanaged Disk',
+  to create a Virtual Machine in Availability Zones.
+* When creating a Virtual Machine with the azure_rm_virtualmachine,
+  you need to specify explicitly managed_disk_type
+  to change OS disk to 'Managed Disk'.
+  Otherwise, OS disk becomes 'Unmanaged disk'.
+* When creating a data disk with azure_rm_manageddisk,
+  you need to specify explicitly storage_account_type
path: docs/docsite/rst/scenario_guides/guide_azure.rst
text: @user1:
```suggestion
  you need to  explicitly specify the  ``storage_account_type`` parameter
```

diff_hunk: @@ -257,6 +257,31 @@ virtual network already with an existing subnet, you can run the following to cr
         version: latest
 
 
+Creating a Virtual Machine in Availability Zones
+..................................................
+
+If you want to create a Virtual Machines in Availability Zones,
+Note the following:
+
+* Both OS disk and data disk must be a 'Managed Disk', not 'Unmanaged Disk',
+  to create a Virtual Machine in Availability Zones.
+* When creating a Virtual Machine with the azure_rm_virtualmachine,
+  you need to specify explicitly managed_disk_type
path: docs/docsite/rst/scenario_guides/guide_azure.rst
text: @user1:
```suggestion
  you need to explicitly set the ``managed_disk_type`` parameter
```

diff_hunk: @@ -257,6 +257,31 @@ virtual network already with an existing subnet, you can run the following to cr
         version: latest
 
 
+Creating a Virtual Machine in Availability Zones
+..................................................
+
+If you want to create a Virtual Machines in Availability Zones,
+Note the following:
+
+* Both OS disk and data disk must be a 'Managed Disk', not 'Unmanaged Disk',
+  to create a Virtual Machine in Availability Zones.
+* When creating a Virtual Machine with the azure_rm_virtualmachine,
+  you need to specify explicitly managed_disk_type
+  to change OS disk to 'Managed Disk'.
+  Otherwise, OS disk becomes 'Unmanaged disk'.
+* When creating a data disk with azure_rm_manageddisk,
+  you need to specify explicitly storage_account_type
+  to make it a 'Managed Disk'.
+  Otherwise, the data disk will be 'Unmanaged disk'.
+* 'Managed Disk' does not require 'Storage Account' or 'Storage Container'
+  unlike 'Unmanaged Disk'.
+  In particular, note that once a Virtual Machine is created on an 'Unmanaged disk',
+  an unnecessary 'Storage container' named "vhds" is automatically created.
+* When creating an IP address with azure_rm_publicipaddress,
+  it is necessary to specify 'standard' in the 'sku' property.
path: docs/docsite/rst/scenario_guides/guide_azure.rst
text: @user1:
```suggestion
  you must set the  ``sku`` parameter to ``standard``.
```

diff_hunk: @@ -257,6 +257,31 @@ virtual network already with an existing subnet, you can run the following to cr
         version: latest
 
 
+Creating a Virtual Machine in Availability Zones
+..................................................
+
+If you want to create a Virtual Machines in Availability Zones,
path: docs/docsite/rst/scenario_guides/guide_azure.rst
text: @user1:
```suggestion
If you want to create a VM in an availability zone,
```