Skip to content

Commit 5e19cba

Browse files
authored
Update custom-data.md
1 parent 8eb7fac commit 5e19cba

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-machines/custom-data.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Azure currently supports two provisioning agents:
6767
* Provisioning.DecodeCustomData
6868
* Provisioning.ExecuteCustomData
6969

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.
7171

7272
To troubleshoot custom data execution, review */var/log/waagent.log*
7373

@@ -79,13 +79,13 @@ To troubleshoot custom data execution, review the troubleshooting [documentation
7979

8080
## FAQ
8181
### 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:
8383
* Existing instances in the VMSS will not get the updated custom data, only until they are reimaged.
8484
* Existing instances in the VMSS that are upgraded will not get the updated custom data.
8585
* New instances will receive the new custom data.
8686

8787
### 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).
8989

9090

9191
### Is custom data made available in IMDS?

0 commit comments

Comments
 (0)