Merge pull request #253732 from MicrosoftDocs/main

10/04 OOB Publish at 7am

Author: huypub

articles/active-directory/external-identities/hybrid-on-premises-to-cloud.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: B2B
 ms.topic: how-to
-ms.date: 11/17/2022
+ms.date: 10/04/2023
 
 ms.author: cmulligan
 author: csmulligan
@@ -21,10 +21,10 @@ ms.collection: M365-identity-device-management
 
 Before Microsoft Entra ID, organizations with on-premises identity systems have traditionally managed partner accounts in their on-premises directory. In such an organization, when you start to move apps to Microsoft Entra ID, you want to make sure your partners can access the resources they need. It shouldn't matter whether the resources are on-premises or in the cloud. Also, you want your partner users to be able to use the same sign-in credentials for both on-premises and Microsoft Entra resources. 
 
-If you create accounts for your external partners in your on-premises directory (for example, you create an account with a sign-in name of "msullivan" for an external user named Maria Sullivan in your partners.contoso.com domain), you can now sync these accounts to the cloud. Specifically, you can use [Microsoft Entra Connect](../hybrid/connect/whatis-azure-ad-connect.md) to sync the partner accounts to the cloud, which creates a user account with UserType = Guest. This enables your partner users to access cloud resources using the same credentials as their local accounts, without giving them more access than they need.
+If you create accounts for your external partners in your on-premises directory (for example, you create an account with a sign-in name of "msullivan" for an external user named Maria Sullivan in your partners.contoso.com domain), you can now sync these accounts to the cloud. Specifically, you can use [Microsoft Entra Connect](../hybrid/connect/whatis-azure-ad-connect.md) to sync the partner accounts to the cloud, which creates a user account with UserType = Guest. This enables your partner users to access cloud resources using the same credentials as their local accounts, without giving them more access than they need. For more information about converting local guest accounts see [Convert local guest accounts to Microsoft Entra B2B guest accounts](/azure/active-directory/architecture/10-secure-local-guest). 
 
 > [!NOTE]
-> See also how to [invite internal users to B2B collaboration](invite-internal-users.md). With this feature, you can invite internal guest users to use B2B collaboration, regardless of whether you've synced their accounts from your on-premises directory to the cloud. Once the user accepts the invitation to use B2B collaboration, they'll be able to use their own identities and credentials to sign in to the resources you want them to access. You won’t need to maintain passwords or manage account lifecycles.
+> See also how to [invite internal users to B2B collaboration](invite-internal-users.md). With this feature, you can invite internal guest users to use B2B collaboration, regardless of whether you've synced their accounts from your on-premises directory to the cloud. Once the user accepts the invitation to use B2B collaboration, they'll be able to use their own identities and credentials to sign in to the resources you want them to access. You won’t need to maintain passwords or manage account lifecycles. 
 
 ## Identify unique attributes for UserType
 
@@ -49,4 +49,4 @@ For implementation instructions, see [Enable synchronization of UserType](../hyb
 
 - [Microsoft Entra B2B collaboration for hybrid organizations](hybrid-organizations.md)
 - [Grant B2B users in Microsoft Entra ID access to your on-premises applications](hybrid-cloud-to-on-premises.md)
-- For an overview of Microsoft Entra Connect, see [Integrate your on-premises directories with Microsoft Entra ID](../hybrid/whatis-hybrid-identity.md).
+

articles/ai-services/speech-service/includes/quickstarts/keyword-recognition/csharp.md

@@ -30,6 +30,8 @@ var keywordModel = KeywordRecognitionModel.FromFile("your/path/to/Activate_devic
 using var audioConfig = AudioConfig.FromDefaultMicrophoneInput();
 using var keywordRecognizer = new KeywordRecognizer(audioConfig);
 ```
+> [!IMPORTANT]
+> If you prefer testing a keyword model directly with audio samples via the `AudioConfig.fromStreamInput()` method, make sure you use samples that have at least 1.5 seconds of silence before the first keyword. This is to provide an adequate time for the Keyword recognition engine to initialize and to get to the listening state prior to detecting the first keyword.
 
 Next, running keyword recognition is done with one call to `RecognizeOnceAsync()` by passing your model object. This starts a keyword recognition session that lasts until the keyword is recognized. Thus, you generally use this design pattern in multi-threaded applications, or in use cases where you may be waiting for a wake-word indefinitely.
 

articles/azure-netapp-files/create-active-directory-connections.md

@@ -46,7 +46,7 @@ Several features of Azure NetApp Files require that you have an Active Directory
     * Alternatively, an AD domain user account with `msDS-SupportedEncryptionTypes` write permission on the AD connection admin account can also be used to set the Kerberos encryption type property on the AD connection admin account. 
 
     >[!NOTE]
-    >It's _not_ recommended nor required to add the Azure NetApp Files AD admin account to the AD domain groups listed above. Nor is it recommended or required to grant `msDS-SupportedEncryptionTypes` write permission to the Azure NetApp Files AD admin account.  
+    >When you modify the setting to enable AES on the AD connection admin account, it is a best practice to use a user account that has write permission to the AD object that is not the Azure NetApp Files AD admin. You can do so with another domain admin account or by delegating control to an account. For more information, see [Delegating Administration by Using OU Objects](/windows-server/identity/ad-ds/plan/delegating-administration-by-using-ou-objects). 
 
     If you set both AES-128 and AES-256 Kerberos encryption on the admin account of the AD connection, the highest level of encryption supported by your AD DS will be used.
 

articles/communication-services/concepts/numbers/phone-number-management-for-ireland.md

@@ -45,14 +45,11 @@ More details on eligible subscription types are as follows:
 ## Azure subscription billing locations where Ireland phone numbers are available
 | Country/Region |
 | :---------- |
-|Canada|
 |Denmark|
 |Ireland|
 |Italy|
-|Puerto Rico|
 |Sweden|
-|United Kingdom|
-|United States|
+
 
 
 ## Find information about other countries/regions

articles/communication-services/concepts/numbers/phone-number-management-for-italy.md

@@ -51,6 +51,7 @@ More details on eligible subscription types are as follows:
 | :---------- |
 |Canada|
 |Denmark|
+|France|
 |Ireland|
 |Italy|
 |Puerto Rico|

articles/index.yml

@@ -829,6 +829,15 @@ productDirectory:
         - devops
       url: load-testing/index.yml
     # Card
+    - title: Microsoft Playwright Testing (Preview)
+      summary: Run end-to-end Playwright tests at scale
+      imageSrc: ./media/index/playwright-testing-icon.svg
+      azureCategories:
+        - devops
+        - developer-tools
+        - web
+      url: playwright-testing/index.yml
+    # Card
     - title: Azure Managed Grafana
       summary: Deploy Grafana dashboards as a fully managed Azure service
       imageSrc: ./media/index/managed-grafana.svg