Merge pull request #314362 from v-thepet/sc6

Freshness Edit: Service Connector 6

Author: v-dirichards

articles/service-connector/known-limitations.md

@@ -1,35 +1,37 @@
 ---
 title: Service Connector limitations
-description: Learn about current limitations in Service Connector used to connect apps and Cloud services in Azure.
+description: Learn about current limitations when you use Service Connector to connect apps and cloud services in Azure.
 titleSuffix: Service Connector
 ms.service: service-connector
 ms.topic: troubleshooting
-ms.date: 10/22/2024
+ms.date: 04/06/2026
 ms.author: malev
 author: maud-lv
+#customer intent: As a Service Connector user, I need to understand the known limitations of Service Connector so I can mitigate these limitations when I use Service Connector to connect my Azure apps and services.
 ---
-# Known limitations of Service Connector
+# Known Service Connector limitations
 
-In this article, learn about Service Connector's existing limitations and how to mitigate them.
+This article describes known Service Connector limitations and ways to mitigate them.
 
-## Limitations to Infrastructure as Code (IaC)
+## Limitations
 
-Service Connector is designed to bring the benefits of easy, secure, and consistent backing service connections to as many Azure services as possible. To do so, Service Connector is developed as an extension resource provider.
+Service Connector is designed as an extension resource provider, so it can bring easy, secure, and consistent backing service connections to as many Azure services as possible. This infrastructure-as-code (IaC) support imposes some limitations, because Service Connector modifies existing infrastructure on the user's behalf.
 
-IaC support comes with some limitations, as Service Connector modifies the infrastructure on the users' behalf. In this scenario, users begin by using Azure Resource Manager (ARM), Bicep, Terraform, or other IaC templates to create resources. Afterwards, they use Service Connector to set up resource connections. During this step, Service Connector modifies resource configurations on behalf of the user. If the user reruns their IaC template at a later time, modifications made by Service Connector disappear as they weren't reflected in the original IaC templates. As an example of this behavior, Azure Container Apps resources deployed with ARM templates usually have the managed identity authentication disabled by default. Service Connector enables the managed identity when setting up connections on the users' behalf. If users trigger the same ARM templates without updating the managed identity settings, the managed identity will be disabled once again in the redeployed Azure Container Apps resource.
+If you use Bicep, Terraform, Azure Resource Manager (ARM), or other IaC templates to create resources, and afterwards use Service Connector to set up resource connections, Service Connector modifies the resource configurations on your behalf. If you later rerun your IaC templates, the modifications Service Connector made disappear, because they weren't included in the original IaC templates.
 
-If you run into any issues when using Service Connector, [file an issue with us](https://github.com/Azure/ServiceConnector/issues/new).
+For example, Azure Container Apps resources deployed with ARM templates usually disable managed identity authentication by default. When Service Connector then sets up connections, it enables managed identity on your behalf. If you trigger the same ARM templates without updating the managed identity settings, managed identity is disabled again in the redeployed Azure Container Apps resources.
 
 ## Solutions
 
-We suggest the following solutions:
+To mitigate the limitations, try the following solutions:
 
-- Reference [how to build connections with IaC tools](how-to-build-connections-with-iac-tools.md) to build your infrastructure or translate your existing infrastructure to IaC templates.
-- If your CI/CD pipelines contain templates of source compute or backing services, we suggested reapplying the templates, adding a sanity check or smoke tests to make sure the application is up and running, then allowing live traffic to the application. The flow adds a verification step before allowing live traffic.
-- When automating Azure Container App code deployments with Service Connector, we recommend the use of [multiple revision mode](../container-apps/revisions.md#revision-modes) to avoid routing traffic to a temporarily nonfunctional app before Service connector can reapply connections.
-- The order in which automation operations are performed matters. Ensure your connection endpoints are there before the connection itself is created. Ideally, create the backing service, then the compute service, and then the connection between the two. This way, Service Connector can configure both the compute service and the backing service appropriately.
+- See [Create connections with IaC tools](how-to-build-connections-with-iac-tools.md) to build your infrastructure or translate your existing infrastructure to IaC templates.
+- If your continuous integration/continuous delivery (CI/CD) pipeline source contains compute or backing service templates, add a liveness check or smoke tests when you reapply the templates. This flow adds a verification step to make sure the application is up and running before allowing live traffic to the application.
+- When you automate Azure Container App code deployments with Service Connector, use [multiple revision mode](/azure/container-apps/revisions#revision-modes). This mode avoids routing traffic to a temporarily nonfunctional app before Service Connector can reapply connections.
+- The order of automation operations matters. Ensure your connection endpoints exist before the connection itself is created. Ideally, create the backing service, then create the compute service, and then create the connection between the two services. Service Connector can then configure both the compute service and the backing service appropriately.
+- If you run into issues when using Service Connector, [file an issue](https://github.com/Azure/ServiceConnector/issues/new).
 
-## Next steps
+## Related content
 
-> [!div class="nextstepaction"]
-> [Service Connector troubleshooting guidance](./how-to-troubleshoot-front-end-error.md)
+- [Service Connector troubleshooting guidance](how-to-troubleshoot-front-end-error.md)
+- [Create connections with IaC tools](how-to-build-connections-with-iac-tools.md)