Merge pull request #281588 from sanchitmehta/sanmeht/new-regions

Add New Regions + Code Interpreter Identifier Warning

Author: prmerger-automator[bot]

articles/container-apps/sessions-code-interpreter.md

@@ -92,6 +92,10 @@ After you create a session pool, your application can interact with sessions in
 
 ### Session identifiers
 
+> [!IMPORTANT]
+> The session identifier is sensitive information which requires you to use a secure process to manage its value. Part of this process requires that your application ensures each user or tenant only has access to their own sessions.
+> Failure to secure access to sessions may result in misuse or unauthorized access to data stored in your users' sessions. For more information, see [Session identifiers](sessions.md#session-identifiers)
+
 When you interact with sessions in a pool, you use a session identifier to reference each session A session identifier is a string that you define that is unique within the session pool. If you're building a web application, you can use the user's ID. If you're building a chatbot, you can use the conversation ID.
 
 If there's a running session with the identifier, the session is reused. If there's no running session with the identifier, a new session is automatically created.

articles/container-apps/sessions.md

@@ -205,9 +205,12 @@ Azure Container Apps dynamic sessions is currently in preview. The following lim
     |--------|------------------|------------------|
     | East Asia | ✔ | ✔ |
     | East US | ✔ | ✔ |
-    | West US 2 | ✔ | ✔ |
+    | Germany West Central | ✔ | ✔ |
+    | Italy North | ✔ | ✔ |
+    | Poland Central | ✔ | ✔ |
     | North Central US | ✔ | - |
-    | North Europe | ✔ | - |
+    | North Europe | ✔ | ✔ |
+    | West US 2 | ✔ | ✔ |
 
 * Logging isn't supported. Your application can log requests to the session pool management API and its responses.