Merge pull request #245730 from MicrosoftDocs/main

7/20/2023 PM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -13338,6 +13338,16 @@
             "redirect_url": "/azure/governance/policy/samples/index",
             "redirect_document_id": false
         },
+        {
+          "source_path_from_root": "/articles/governance/policy/samples/PCIv3_2_1_2018_audit.md",
+          "redirect_url": "/azure/governance/policy/samples/pci-dss-3-2-1",
+          "redirect_document_id": false
+        },
+        {
+          "source_path_from_root": "/articles/governance/policy/samples/pci_dss_v4.0.md",
+          "redirect_url": "/azure/governance/policy/samples/pci-dss-4-0",
+          "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure-policy/create-manage-policy.md",
             "redirect_url": "/azure/governance/policy/tutorials/create-and-manage",

articles/active-directory/fundamentals/whats-new-sovereign-clouds.md

@@ -21,6 +21,53 @@ Azure AD receives improvements on an ongoing basis. To stay up to date with the
 
 This page updates monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in [Archive for What's new in Sovereign Clouds](whats-new-archive.md).
 
+## June 2023 
+
+### General Availability - Apply RegEx Replace to groups claim content 
+
+
+
+**Type:** New feature   
+**Service category:** Enterprise Apps                  
+**Product capability:** SSO             
+
+Today, when group claims are added to tokens Azure Active Directory attempts to include all of the groups the user is a member of.  In larger organizations where users are members of hundreds of groups this can often exceed the limits of what can go in the token.  This feature enables more customers to connect their apps to Azure Active Directory by making connections easier and more robust through automation of the application’s creation process. This specifically allows the set of groups included in the token to be limited to only those that are assigned to the application. For more information, see: [Regex-based claims transformation](../develop/saml-claims-customization.md#regex-based-claims-transformation).
+
+---
+
+### General Availability - Azure Active Directory SSO integration with Cisco Unified Communications Manager
+
+
+
+**Type:** New feature   
+**Service category:** Enterprise Apps                  
+**Product capability:** Platform              
+
+Cisco Unified Communications Manager (Unified CM) provides reliable, secure, scalable, and manageable call control and session management. When you integrate Cisco Unified Communications Manager with Azure Active Directory, you can:
+
+- Control in Azure Active Directory who has access to Cisco Unified Communications Manager.
+- Enable your users to be automatically signed-in to Cisco Unified Communications Manager with their Azure AD accounts.
+- Manage your accounts in one central location - the Azure portal.
+
+
+For more information, see: [Azure Active Directory SSO integration with Cisco Unified Communications Manager](../saas-apps/cisco-unified-communications-manager-tutorial.md).
+
+---
+
+### General Availability - Number Matching for Microsoft Authenticator notifications
+
+**Type:** Plan for Change  
+**Service category:** Microsoft Authenticator App                      
+**Product capability:** User Authentication             
+
+Microsoft Authenticator app’s number matching feature has been Generally Available since Nov 2022! If you haven't already used the rollout controls (via Azure portal Admin UX and MSGraph APIs) to smoothly deploy number matching for users of Microsoft Authenticator push notifications, we highly encourage you to do so. We previously announced that we'll remove the admin controls and enforce the number match experience tenant-wide for all users of Microsoft Authenticator push notifications starting February 27, 2023. After listening to customers, we'll extend the availability of the rollout controls for a few more weeks. Organizations can continue to use the existing rollout controls until May 8, 2023, to deploy number matching in their organizations. Microsoft services will start enforcing the number matching experience for all users of Microsoft Authenticator push notifications after May 8, 2023. We'll also remove the rollout controls for number matching after that date.
+
+If customers don’t enable number match for all Microsoft Authenticator push notifications prior to May 8, 2023, Authenticator users may experience inconsistent sign-ins while the services are rolling out this change. To ensure consistent behavior for all users, we highly recommend you enable number match for Microsoft Authenticator push notifications in advance.
+
+For more information, see: [How to use number matching in multifactor authentication (MFA) notifications - Authentication methods policy](../authentication/how-to-mfa-number-match.md)
+
+---
+
 ## May 2023
 
 ### General Availability - Admins can now restrict users from self-service accessing their BitLocker keys

articles/ai-services/openai/concepts/models.md

@@ -5,7 +5,7 @@ description: Learn about the different model capabilities that are available wit
 ms.service: cognitive-services
 ms.subservice: openai
 ms.topic: conceptual 
-ms.date: 07/12/2023
+ms.date: 07/20/2023
 ms.custom: event-tier1-build-2022, references_regions, build-2023, build-2023-dataai
 manager: nitinme
 author: mrbullwinkle #ChrisHMSFT
@@ -65,11 +65,10 @@ Currently, we offer three families of Embeddings models for different functional
 
 The DALL-E models, currently in preview, generate images from text prompts that the user provides.
 
-
 ## Model summary table and region availability
 
 > [!IMPORTANT]
-> South Central US is temporarily unavailable for creating new resources due to high demand.
+> South Central US and East US are temporarily unavailable for creating new resources and deployments due to high demand.
 
 ### GPT-4 models
 
@@ -92,8 +91,8 @@ GPT-3.5 Turbo is used with the Chat Completion API. GPT-3.5 Turbo (0301) can als
 |  Model ID  |   Base model Regions   | Fine-Tuning Regions | Max Request (tokens) | Training Data (up to)  |
 |  --------- |  --------------------- | ------------------- | -------------------- | ---------------------- |
 | `gpt-35-turbo`<sup>1</sup> (0301) | East US, France Central, South Central US, UK South, West Europe | N/A | 4,096 | Sep 2021 |
-| `gpt-35-turbo` (0613) | East US, France Central, UK South | N/A | 4,096 | Sep 2021 |
-| `gpt-35-turbo-16k` (0613) | East US, France Central, UK South | N/A | 16,384 | Sep 2021 |
+| `gpt-35-turbo` (0613) | East US, France Central, Japan East, North Central US, UK South | N/A | 4,096 | Sep 2021 |
+| `gpt-35-turbo-16k` (0613) | East US, France Central, Japan East, North Central US, UK South | N/A | 16,384 | Sep 2021 |
 
 <sup>1</sup> Version `0301` of gpt-35-turbo will be retired on January 4, 2024.  See [model updates](#model-updates) for model upgrade behavior.
 

articles/ai-services/openai/faq.yml

@@ -48,7 +48,7 @@ sections:
       - question: |
           I am trying to use embeddings and received the error "InvalidRequestError: Too many inputs. The max number of inputs is 1." How do I fix this?
         answer: | 
-          This error typically occurs when you try to send a batch of text to embed in a single API request as an array. Currently Azure OpenAI does not support batching with embedding requests. Embeddings API calls should consist of a single string input per request. The string can be up to 8191 tokens in length when using the text-embedding-ada-002 (Version 2) model.
+          This error typically occurs when you try to send a batch of text to embed in a single API request as an array. Currently Azure OpenAI only supports arrays of embeddings with multiple inputs for the `text-embedding-ada-002` Version 2 model. This model version supports an array consisting of up to 16 inputs per API request. The array can be up to 8191 tokens in length when using the text-embedding-ada-002 (Version 2) model.
       - question: |
           Where can I read about better ways to use Azure OpenAI to get the responses I want from the service?
         answer: | 

articles/ai-services/openai/how-to/quota.md

@@ -8,14 +8,19 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: openai
 ms.topic: how-to
-ms.date: 07/18/2023
+ms.date: 07/20/2023
 ms.author: mbullwin
 ---
 
 # Manage Azure OpenAI Service quota
 
 Quota provides the flexibility to actively manage the allocation of rate limits across the deployments within your subscription. This article walks through the process of managing your Azure OpenAI quota.
 
+## Prerequisites
+
+> [!IMPORTANT]
+> Quota requires the **Cognitive Services Usages Reader** role. This role provides the minimal access necessary to view quota usage across an Azure subscription. This role can be found in the Azure portal under **Subscriptions** > **Access control (IAM)** > **Add role assignment** > search for **Cognitive Services Usages Reader**.
+
 ## Introduction to quota
 
 Azure OpenAI's quota feature enables assignment of rate limits to your deployments, up-to a global limit called your “quota.”  Quota is assigned to your subscription on a per-region, per-model basis in units of **Tokens-per-Minute (TPM)**. When you onboard a subscription to Azure OpenAI, you'll receive default quota for most available models. Then, you'll assign TPM to each deployment as it is created, and the available quota for that model will be reduced by that amount. You can continue to create deployments and assign them TPM until you reach your quota limit. Once that happens, you can only create new deployments of that model by reducing the TPM assigned to other deployments of the same model (thus freeing TPM for use), or by requesting and being approved for a model quota increase in the desired region.

articles/ai-services/openai/how-to/switching-endpoints.md

@@ -8,7 +8,7 @@ ms.service: cognitive-services
 ms.subservice: openai
 ms.custom: devx-track-python
 ms.topic: how-to
-ms.date: 05/24/2023
+ms.date: 07/20/2023
 manager: nitinme
 ---
 
@@ -161,9 +161,9 @@ embedding = openai.Embedding.create(
 </tr>
 </table>
 
-## Azure OpenAI embeddings doesn't support multiple inputs
+## Azure OpenAI embeddings multiple input support
 
-Many examples show passing multiple inputs into the embeddings API. For Azure OpenAI, currently we must pass a single text input per call.
+OpenAI currently allows a larger number of array inputs with text-embedding-ada-002. Azure OpenAI currently supports input arrays up to 16 for text-embedding-ada-002 Version 2. Both require the max input token limit per API request to remain under 8191 for this model.
 
 <table>
 <tr>
@@ -173,7 +173,7 @@ Many examples show passing multiple inputs into the embeddings API. For Azure Op
 <td>
 
 ```python
-inputs = ["A", "B", "C"]
+inputs = ["A", "B", "C"] 
 
 embedding = openai.Embedding.create(
   input=inputs,
@@ -187,14 +187,13 @@ embedding = openai.Embedding.create(
 <td>
 
 ```python
-inputs = ["A", "B", "C"]
-
-for text in inputs:
-    embedding = openai.Embedding.create(
-        input=text,
-        deployment_id="text-embedding-ada-002"
-        #engine="text-embedding-ada-002"
-    )
+inputs = ["A", "B", "C"] #max array size=16
+
+embedding = openai.Embedding.create(
+  input=inputs,
+  deployment_id="text-embedding-ada-002"
+  #engine="text-embedding-ada-002"
+)
 ```
 
 </td>

articles/ai-services/openai/whats-new.md

@@ -8,7 +8,7 @@ ms.author: mbullwin
 ms.service: cognitive-services
 ms.subservice: openai
 ms.topic: whats-new
-ms.date: 06/12/2023
+ms.date: 07/20/2023
 recommendations: false
 keywords:  
 ---
@@ -17,10 +17,14 @@ keywords:
 
 ## July 2023
 
-### Support for function calling 
+### Support for function calling
 
 - [Azure OpenAI now supports function calling](./how-to/function-calling.md) to enable you to work with functions in the chat completions API.
 
+### Embedding input array increase
+
+- Azure OpenAI now [supports arrays with up to 16 inputs](./how-to/switching-endpoints.md#azure-openai-embeddings-multiple-input-support) per API request with text-embedding-ada-002 Version 2.
+
 ## June 2023
 
 ### Use Azure OpenAI on your own data (preview)

articles/api-management/api-management-howto-app-insights.md

@@ -90,7 +90,7 @@ You can specify loggers on different levels:
 
 Specifying *both*:
 - By default, the single API logger (more granular level) overrides the one for all APIs.
-- If the loggers configured at the two levels are different, and you need both loggers to receive telemetry (multiplexing), please contact Microsoft Support. 
+- If the loggers configured at the two levels are different, and you need both loggers to receive telemetry (multiplexing), please contact Microsoft Support. Please note that multiplexing is not supported if you're using the same logger (Application Insights destination) at the "All APIs" level and the single API level. For multiplexing to work correctly, you must configure different loggers at the "All APIs" and individual API level and request assistance from Microsoft support to enable multiplexing for your service.
 
 ## What data is added to Application Insights
 

articles/api-management/cosmosdb-data-source-policy.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: api-management
 ms.custom: devx-track-azurecli
-ms.topic: reference
+ms.topic: article
 ms.date: 06/07/2023
 ms.author: danlep
 ---

articles/api-management/http-data-source-policy.md

@@ -5,7 +5,7 @@ services: api-management
 author: dlepow
 
 ms.service: api-management
-ms.topic: reference
+ms.topic: article
 ms.date: 03/07/2023
 ms.author: danlep
 ---