add sdk blurb

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/container-apps/dapr-overview.md

@@ -25,7 +25,7 @@ Configure Dapr for your container apps environment with a [Dapr-enabled containe
 | 2     | Dapr                             | The fully managed Dapr APIs are exposed to each container app through a Dapr sidecar. The Dapr APIs can be invoked from your container app via HTTP or gRPC. The Dapr sidecar runs on HTTP port 3500 and gRPC port 50001.                                                         |
 | 3     | Dapr component configuration     | Dapr uses a modular design where functionality is delivered as a component. Dapr components can be shared across multiple container apps. The Dapr app identifiers provided in the scopes array dictate which dapr-enabled container apps load a given component at runtime. |
 
-## Supported Dapr APIs and components
+## Supported Dapr APIs, components, and tooling
 
 ### Managed APIs
 
@@ -51,6 +51,10 @@ To learn more about using _alpha_ Dapr APIs and features, [see the Dapr FAQ][dap
 
 [!INCLUDE [component-support](../../includes/dapr-in-azure/dapr-support-policy.md)]
 
+### Tooling
+
+Azure Container Apps ensures compatibility with Dapr open source tooling, such as SDKs and the CLI. 
+
 ## Limitations
 
 - **Dapr Configuration spec**: Any capabilities that require use of the Dapr configuration spec.