Merge pull request #183949 from MicrosoftDocs/master

1/03 AM Publish

Author: huypub

articles/active-directory/enterprise-users/users-search-enhanced.md

@@ -1,5 +1,5 @@
 ---
-title: User management enhancements (preview) - Azure Active Directory | Microsoft Docs
+title: User management enhancements - Azure Active Directory | Microsoft Docs
 description: Describes how Azure Active Directory enables user search, filtering, and more information about your users.
 services: active-directory
 documentationcenter: ''
@@ -11,42 +11,30 @@ ms.service: active-directory
 ms.subservice: enterprise-users
 ms.workload: identity
 ms.topic: how-to
-ms.date: 01/11/2020
+ms.date: 01/03/2022
 ms.author: curtand
 ms.reviewer: krbain
 ms.custom: it-pro
 
 ms.collection: M365-identity-device-management
 ---
 
-# User management enhancements (preview) in Azure Active Directory
+# User management enhancements in Azure Active Directory
 
-This article describes how to use the user management enhancements preview in the Azure Active Directory (Azure AD) portal. The **All users** and **Deleted users** pages have been updated to provide more information and make it easier to find users. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+This article describes how to use the user management enhancements in the Azure Active Directory (Azure AD) portal. The **All users** and **Deleted users** pages have been updated to provide more information and make it easier to find users.
 
-Changes in the preview include:
+Enhancements include:
 
 - More visible user properties including object ID, directory sync status, creation type, and identity issuer
-- Search now allows substring search and combined search of names, emails, and object IDs
+- Search allows substring search and combined search of names, emails, and object IDs
 - Enhanced filtering by user type (member, guest, none), directory sync status, creation type, company name, and domain name
-- New sorting capabilities on properties like name and user principal name
-- A new total users count that updates with searches or filters
+- Sorting capabilities on properties like name and user principal name
+- Total users count that updates with searches or filters
 
 > [!NOTE]
-> This preview is currently not available for Azure AD B2C tenants.
+> These enhancements are not currently available for Azure AD B2C tenants.
 
-## Find the preview
-
-The preview is turned on by default, so you can use it right away. You can check out the latest features and improvements by selecting **Preview features** on the **All users** page. All pages that have been updated as part of this preview will display a preview tag. If you are having any issues, you can switch back to the legacy experience:
-
-1. Sign in to the [Azure AD admin center](https://aad.portal.azure.com) and select **Users**.
-1. From the **Users – All users** page, select the banner at the top of the page.
-1. In the **Preview features** pane, turn **Enhanced user management** off.
-
-   ![How and where to turn Enhanced User Management on and off](./media/users-search-enhanced/enable-preview.png)
-
-We appreciate your feedback so that we can improve our experience.
-
-## More user properties
+## User properties enhanced
 
 We’ve made some changes to the columns available on the **All users** and **Deleted users** pages. In addition to the existing columns we provide for managing your list of users, we've added a few more columns.
 

articles/active-directory/saas-apps/workplace-by-facebook-provisioning-tutorial.md

@@ -210,7 +210,7 @@ POST https://graph.microsoft.com/beta/servicePrincipals/[object-id]/synchronizat
 9. Return to the first web browser window and select the Provisioning tab for your application. Your configuration will have been reset. You can confirm the upgrade has taken place by confirming the Job ID starts with “FacebookWorkplace”. 
 
 10. Update the tenant URL in the Admin Credentials section to the following: https://scim.workplace.com/  
-![Screenshot of Admin Credentials in the Workplace by Facebook app in the Azure portalt](./media/workplace-by-facebook-provisioning-tutorial/credentials.png)
+![Screenshot of Admin Credentials in the Workplace by Facebook app in the Azure portalt](./media/workplace-by-facebook-provisioning-tutorial/provisionings.png)
 
 11. Restore any previous changes you made to the application (Authentication details, Scoping filters, Custom attribute mappings) and re-enable provisioning. 
 

articles/aks/private-clusters.md

@@ -137,18 +137,11 @@ az extension add --name aks-preview
 az extension update --name aks-preview
 ```
 
-### Create a private AKS cluster with Custom Private DNS Zone
-
-```azurecli-interactive
-# Custom Private DNS Zone name should be in format "privatelink.<region>.azmk8s.io"
-az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <ResourceId> --private-dns-zone <custom private dns zone ResourceId>
-```
-
-### Create a private AKS cluster with Custom Private DNS SubZone
+### Create a private AKS cluster with Custom Private DNS Zone or Private DNS SubZone
 
 ```azurecli-interactive
 # Custom Private DNS Zone name should be in format "<subzone>.privatelink.<region>.azmk8s.io"
-az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <ResourceId> --private-dns-zone <custom private dns zone ResourceId>
+az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <ResourceId> --private-dns-zone <custom private dns zone or custom private dns subzone ResourceId>
 ```
 
 ### Create a private AKS cluster with Custom Private DNS Zone and Custom Subdomain
@@ -218,4 +211,4 @@ As mentioned, virtual network peering is one way to access your private cluster.
 [express-route-or-vpn]: ../expressroute/expressroute-about-virtual-network-gateways.md
 [devops-agents]: /azure/devops/pipelines/agents/agents
 [availability-zones]: availability-zones.md
-[command-invoke]: command-invoke.md
+[command-invoke]: command-invoke.md

articles/aks/spark-job.md

@@ -335,7 +335,7 @@ Check out Spark documentation for more details.
 [docker-hub]: https://docs.docker.com/docker-hub/
 [java-install]: /azure/developer/java/fundamentals/java-support-on-azure
 [maven-install]: https://maven.apache.org/install.html
-[sbt-install]: https://www.scala-sbt.org/1.0/docs/Setup.html
+[sbt-install]: https://www.scala-sbt.org/1.x/docs/Setup.html
 [spark-docs]: https://spark.apache.org/docs/latest/running-on-kubernetes.html
 [spark-kubernetes-earliest-version]: https://spark.apache.org/releases/spark-release-2-3-0.html
 [spark-quickstart]: https://spark.apache.org/docs/latest/quick-start.html

articles/azure-arc/data/create-postgresql-hyperscale-server-group-azure-portal.md

@@ -62,7 +62,7 @@ After you deployed an Arc data controller enabled for Direct connectivity mode,
 
 ### Option 1: Deploy from the Azure Marketplace
 1. Open a browser to the following URL [https://portal.azure.com](https://portal.azure.com)
-2. In the search window at the top of the page search for "*azure arc postgres*" in the Azure Market Place and select **Azure Database for PostgreSQL server groups - Azure Arc**.
+2. In the search window at the top of the page search for "*azure arc postgres*" in the Azure Market Place and select **Azure Arc-enabled PostgreSQL Hyperscale server groups**.
 3. In the page that opens, click **+ Create** at the top left corner. 
 4. Fill in the form like you deploy an other Azure resource.
 

articles/azure-monitor/insights/sql-insights-troubleshoot.md

@@ -4,7 +4,7 @@ description: Learn how to troubleshoot SQL insights in Azure Monitor.
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 11/03/2021
+ms.date: 1/3/2022
 ---
 
 # Troubleshoot SQL insights (preview)
@@ -28,9 +28,9 @@ SQL insights uses the following query to retrieve this information:
 
 ```kusto
 InsightsMetrics 
-    | extend Tags = todynamic(Tags) 
-    | extend SqlInstance = tostring(Tags.sql_instance) 
-    | where TimeGenerated > ago(10m) and isnotempty(SqlInstance) and Namespace == 'sqlserver_server_properties' and Name == 'uptime' 
+    | extend Tags = todynamic(Tags) 
+    | extend SqlInstance = tostring(Tags.sql_instance) 
+    | where TimeGenerated > ago(10m) and isnotempty(SqlInstance) and Namespace == 'sqlserver_server_properties' and Name == 'uptime' 
 ```
 
 Check if any logs from Telegraf help identify the root cause the problem. If there are log entries, you can select **Not collecting** and check the logs and troubleshooting info for common problems. 
@@ -79,19 +79,22 @@ To see error messages from the telegraf service, run it manually by using the fo
 
 Check [prerequisites](../agents/azure-monitor-agent-install.md#prerequisites) for the Azure Monitor agent. 
 
-
-Service logs:  
+Prior to Azure Monitoring Agent v1.12, mdsd service logs were located in:
 - `/var/log/mdsd.err`
 - `/var/log/mdsd.warn`
 - `/var/log/mdsd.info`
 
+From v1.12 onward, service logs are located in:
+- `/var/opt/microsoft/azuremonitoragent/log/`
+- `/etc/opt/microsoft/azuremonitoragent/`
+
 To see recent errors: `tail -n 100 -f /var/log/mdsd.err`
 
 If you need to contact support, collect the following information: 
 
 - Logs in `/var/log/azure/Microsoft.Azure.Monitor.AzureMonitorLinuxAgent/` 
 - Log in `/var/log/waagent.log` 
-- Logs in `/var/log/mdsd*`
+- Logs in `/var/log/mdsd*`, or logs in `/var/opt/microsoft/azuremonitoragent/log/` and `/etc/opt/microsoft/azuremonitoragent/`.
 - Files in `/etc/mdsd.d/`
 - File `/etc/default/mdsd`
 

articles/cognitive-services/QnAMaker/How-To/improve-knowledge-base.md

@@ -20,7 +20,7 @@ Active Learning alters the Knowledge Base or Search Service after you approve th
 
 ## Turn on active learning
 
-In order to see suggested questions, you must [turn on active learning](../index.yml) for your QnA Maker resource.
+In order to see suggested questions, you must [turn on active learning](../How-To/use-active-learning.md#turn-on-active-learning-for-alternate-questions) for your QnA Maker resource.
 
 ## View suggested questions
 

articles/communication-services/concepts/teams-endpoint.md

@@ -14,10 +14,9 @@ ms.subservice: teams-interop
 ---
 # Build a custom Teams endpoint
 
-> [!IMPORTANT]
-> To enable or disable the custom Teams endpoint experience, [complete and submit this form](https://forms.office.com/r/B8p5KqCH19).
+[!INCLUDE [Public Preview](../includes/public-preview-include-document.md)]
 
-You can use Azure Communication Services to build custom Teams endpoints to communicate with the Microsoft Teams client or other custom Teams endpoints. With a custom Teams endpoint, you can customize a voice, video, chat, and screen-sharing experience for Teams users.
+You can use Azure Communication Services and Graph API to build custom Teams endpoints to communicate with the Microsoft Teams client or other custom Teams endpoints. With a custom Teams endpoint, you can customize a voice, video, chat, and screen-sharing experience for Teams users.
 
 You can use the Azure Communication Services Identity SDK to exchange Azure Active Directory (Azure AD) access tokens of Teams users for Communication Identity access tokens. The diagrams in the next sections demonstrate multitenant use cases, where fictional company Fabrikam is the customer of fictional company Contoso.
 
@@ -39,7 +38,7 @@ Optionally, you can also use custom Teams endpoints to integrate chat capabiliti
 
 |   Permission    |  Display string   |  Description | Admin consent required | Microsoft account supported |
 |:--- |:--- |:--- |:--- |:--- |
-| _`https://auth.msft.communication.azure.com/VoIP`_ | Manage calls in Teams | Start, join, forward, transfer, or leave Teams calls and update call properties. | No | No |
+| _`https://auth.msft.communication.azure.com/Teams.ManageCalls`_ | Manage calls in Teams | Start, join, forward, transfer, or leave Teams calls and update call properties. | No | No |
 
 ### Application permissions
 
@@ -48,8 +47,10 @@ None.
 ### Roles for granting consent on behalf of a company
 
 - Global admin
-- Application admin (only in private preview)
-- Cloud application admin (only in private preview)
+- Application admin
+- Cloud application admin
+
+Find more details in [Azure Active Directory documentation](https://docs.microsoft.com/azure/active-directory/roles/permissions-reference).
 
 ## Next steps
 

articles/communication-services/toc.yml

@@ -130,6 +130,10 @@ items:
         href: concepts/teams-interop.md
       - name: Join a Teams meeting
         href: concepts/join-teams-meeting.md
+      - name: Custom Teams Endpoint
+        items:
+          - name: Custom Teams endpoint overview
+            href: concepts/teams-endpoint.md
   - name: Telephony
     items:
       - name: Telephony Concepts

articles/cosmos-db/analytical-store-introduction.md

@@ -261,21 +261,24 @@ The well-defined schema representation creates a simple tabular representation o
 
 ```SQL
 SELECT CAST (num as float) as num
-FROM OPENROWSET(​PROVIDER = 'CosmosDB',
+FROM OPENROWSET(PROVIDER = 'CosmosDB',
                 CONNECTION = '<your-connection',
                 OBJECT = 'IntToFloat',
                 SERVER_CREDENTIAL = 'your-credential'
 ) 
 WITH (num varchar(100)) AS [IntToFloat]
 ```
 
-  * Properties that don't follow the base schema data type won't be represented in analytical store. For example, consider the 2 documents below, and that the first one defined the analytical store base schema. The second document, where `id` is `2`, doesn't have a well-defined schema since property `"a"` is a string and the first document has `"a"` as a number. In this case, the analytical store registers the data type of `"a"` as `integer` for lifetime of the container. The second document will still be included in analytical store, but its `"a"` property will not.
+  * Properties that don't follow the base schema data type won't be represented in analytical store. For example, consider the documents below: the first one defined the analytical store base schema. The second document, where `id` is `"2"`, **doesn't** have a well-defined schema since property `"code"` is a string and the first document has `"code"` as a number. In this case, the analytical store registers the data type of `"code"` as `integer` for lifetime of the container. The second document will still be included in analytical store, but its `"code"` property will not.
 
-    * `{"id": "1", "a":123}` 
-    * `{"id": "2", "a": "str"}`
+    * `{"id": "1", "code":123}` 
+    * `{"id": "2", "code": "123"}`
 
  > [!NOTE]
- > This condition above doesn't apply for null properties. For example, `{"a":123} and {"a":null}` is still well defined.
+ > The condition above doesn't apply for null properties. For example, `{"a":123} and {"a":null}` is still well defined.
+
+> [!NOTE]
+ > The condition above doesn't change if you update `"code"` of document `"1"` to a string in your transactional store. In analytical store, `"code"` will be kept as `integer` since currently we don't support schema reset.
 
 * Array types must contain a single repeated type. For example, `{"a": ["str",12]}` is not a well-defined schema because the array contains a mix of integer and string types.