Skip to content

Commit 709b9d6

Browse files
Merge pull request #231687 from mumian/0322-export-limitation
add an export limitation
2 parents 23f89d5 + 330b6f5 commit 709b9d6

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

includes/resource-manager-export-template-limitations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,14 @@
22
author: tfitzmac
33
ms.service: azure-resource-manager
44
ms.topic: include
5-
ms.date: 12/16/2021
5+
ms.date: 03/22/2023
66
ms.author: tomfitz
77
---
88

99
## Limitations
1010

11+
Export is not guaranteed to succeed. Export is not a reliable way to turn pre-existing resources into templates that are usable in production. It is better to create resources from scratch using hand-written [Bicep file](../articles/azure-resource-manager/bicep/overview.md), [ARM template](../articles/azure-resource-manager/templates/overview.md) or [terraform](/azure/developer/terraform/overview).
12+
1113
When exporting from a resource group or resource, the exported template is generated from the [published schemas](https://github.com/Azure/azure-resource-manager-schemas/tree/master/schemas) for each resource type. Occasionally, the schema doesn't have the latest version for a resource type. Check your exported template to make sure it includes the properties you need. If necessary, edit the exported template to use the API version you need.
1214

1315
Some password parameters might be missing from the exported templates. You need to check [template reference](/azure/templates), and manually add these parameters before you can use the templates to deploy resources.

0 commit comments

Comments
 (0)