Link IMPORTANT callout to Registry artifact requirements section

jlian · jlian · commit 3da5d60715b1 · 2026-03-24T15:37:42.000-07:00
diff --git a/articles/iot-operations/develop-edge-apps/howto-deploy-wasm-graph-definitions.md b/articles/iot-operations/develop-edge-apps/howto-deploy-wasm-graph-definitions.md
@@ -149,7 +149,7 @@ Once you have the sample modules and graphs, push them to your container registr
 > | Graph definition | `application/vnd.microsoft.aio.graph.v1+yaml` | `application/yaml` |
 > | WASM module | `application/vnd.module.wasm.content.layer.v1+wasm` | `application/wasm` |
 >
-> If you use a CI/CD pipeline or other tooling to copy artifacts between registries, verify that it preserves these media types. Some tools strip or replace artifact metadata during transfer, which causes the artifacts to silently disappear from the operations experience.
+> If you use a CI/CD pipeline or other tooling to copy artifacts between registries, verify that it preserves these media types. Some tools strip or replace artifact metadata during transfer, which causes the artifacts to silently disappear from the operations experience. For more information, see [Registry artifact requirements](#registry-artifact-requirements).
 
 To ensure the graphs and modules are visible in the operations experience web UI, add the `--config` and `--artifact-type` flags as shown in the following example:
 

Original file line number	Diff line number	Diff line change
`@@ -149,7 +149,7 @@ Once you have the sample modules and graphs, push them to your container registr`
`149`	`149`	> \| Graph definition \| `application/vnd.microsoft.aio.graph.v1+yaml` \| `application/yaml` \|
`150`	`150`	> \| WASM module \| `application/vnd.module.wasm.content.layer.v1+wasm` \| `application/wasm` \|
`151`	`151`	`>`
`152`		`-> If you use a CI/CD pipeline or other tooling to copy artifacts between registries, verify that it preserves these media types. Some tools strip or replace artifact metadata during transfer, which causes the artifacts to silently disappear from the operations experience.`
	`152`	`+> If you use a CI/CD pipeline or other tooling to copy artifacts between registries, verify that it preserves these media types. Some tools strip or replace artifact metadata during transfer, which causes the artifacts to silently disappear from the operations experience. For more information, see [Registry artifact requirements](#registry-artifact-requirements).`
`153`	`153`
`154`	`154`	To ensure the graphs and modules are visible in the operations experience web UI, add the `--config` and `--artifact-type` flags as shown in the following example:
`155`	`155`