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/linux/image-builder-troubleshoot.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -354,6 +354,9 @@ The `customization.log` file includes the following stages:
354
354
- Ensure that Azure Policy and Firewall allow connectivity to remote resources.
355
355
- Output comments to the console by using `Write-Host` or `echo`. Doing so lets you search the *customization.log* file.
356
356
357
+
358
+
## Troubleshoot common build errors
359
+
357
360
### The template deployment failed because of policy violation
358
361
359
362
#### Error
@@ -372,13 +375,11 @@ The `customization.log` file includes the following stages:
372
375
373
376
#### Cause
374
377
375
-
When using a key vaults with public access disabled. At this time, Azure Image Builder doesn't support this configuration.
378
+
The above policy violation error is a result of using an Azure Key Vault with public access disabled. At this time, Azure Image Builder doesn't support this configuration.
376
379
377
380
#### Solution
378
381
379
-
KVs to be created with public access enabled.
380
-
381
-
## Troubleshoot common build errors
382
+
The Azure Key Vault must be created with public access enabled.
0 commit comments