Skip to content

Commit 9acdf69

Browse files
authored
[APIM] Update automate-portal-deployments.md
Supportability item
1 parent ac923d1 commit 9acdf69

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/api-management/automate-portal-deployments.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ You can use the API to automate migration of content between two API Management
2222
> [!WARNING]
2323
> The script removes contents of the developer portal in your destination API Management service. If you're concerned about it, make sure you perform a backup.
2424
25+
> [!NOTE]
26+
> You can't use the migration scripts to migrate developer portal content between an API Management instance in a classic tier (for example, Standard) to an instance in a v2 tier (for example, Standard v2).
27+
2528
> [!NOTE]
2629
> If you're using a self-hosted portal with an explicitly defined custom storage account to host media files (i.e., you define the `blobStorageUrl` setting in the `config.design.json` configuration file), you need to use the original `scripts/migrate.js` [script](https://github.com/Azure/api-management-developer-portal/blob/master/scripts.v2/migrate.js). The original script doesn't work for managed or self-hosted portals with the media storage account managed by API Management. In that case, use the script from the `/scripts.v3` folder instead.
2730
@@ -42,4 +45,4 @@ After the script is successfully executed, the target API Management service sho
4245
Learn more about the developer portal:
4346

4447
- [Azure API Management developer portal overview](api-management-howto-developer-portal.md)
45-
- [Self-host the developer portal](developer-portal-self-host.md)
48+
- [Self-host the developer portal](developer-portal-self-host.md)

0 commit comments

Comments
 (0)