You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/custom-data.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ Azure currently supports two provisioning agents:
67
67
* Provisioning.DecodeCustomData
68
68
* Provisioning.ExecuteCustomData
69
69
70
-
When you enable custom data, and execute a script, it will delay the VM reporting that is it ready or that provisioning has succeeded until the script has completed. If the script exceeds the total VM provisioning time allowance of 40 mins, the VM Create will fail. Note, if the script fails to execute, or errors during executing, this is not deemed a fatal provisioning failure, you will need to create a notification path to alert you for the completion state of the script.
70
+
When you enable custom data, and execute a script, it will delay the VM reporting that is it ready or that provisioning has succeeded until the script has completed. If the script exceeds the total VM provisioning time allowance of 40 mins, the VM Create will fail. Note, if the script fails to execute, or errors during executing, it is not deemed a fatal provisioning failure, you will need to create a notification path to alert you for the completion state of the script.
71
71
72
72
To troubleshoot custom data execution, review */var/log/waagent.log*
73
73
@@ -79,13 +79,13 @@ To troubleshoot custom data execution, review the troubleshooting [documentation
79
79
80
80
## FAQ
81
81
### Can I update custom data after the VM has been created?
82
-
For single VMs, custom data in the VM model cannot be updated, but for VMSS, you can update VMSS custom data via REST API (this will not work for the PS or AZ CLI clients). When you update custom data in the VMSS model, the following will occur:
82
+
For single VMs, custom data in the VM model cannot be updated, but for VMSS, you can update VMSS custom data via REST API (this will not work for the PS or AZ CLI clients). When you update custom data in the VMSS model:
83
83
* Existing instances in the VMSS will not get the updated custom data, only until they are reimaged.
84
84
* Existing instances in the VMSS that are upgraded will not get the updated custom data.
85
85
* New instances will receive the new custom data.
86
86
87
87
### Can I place sensitive values in custom data?
88
-
We advise **not** to store sensitive data in custom data. For additional information, see [Azure Security and encryption best practices](https://docs.microsoft.com/azure/security/fundamentals/data-encryption-best-practices).
88
+
We advise **not** to store sensitive data in custom data. For more information, see [Azure Security and encryption best practices](https://docs.microsoft.com/azure/security/fundamentals/data-encryption-best-practices).
0 commit comments