Merge pull request #213362 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 10/3

Author: ttorble

articles/active-directory/develop/whats-new-docs.md

@@ -5,7 +5,7 @@ services: active-directory
 author: mmacy
 manager: CelesteDG
 
-ms.date: 09/01/2022
+ms.date: 09/03/2022
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: reference
@@ -18,6 +18,19 @@ ms.custom: has-adal-ref
 
 Welcome to what's new in the Microsoft identity platform documentation. This article lists new docs that have been added and those that have had significant updates in the last three months.
 
+## September 2022
+
+### New articles
+
+- [Configure a user-assigned managed identity to trust an external identity provider (preview)](workload-identity-federation-create-trust-user-assigned-managed-identity.md)
+- [Important considerations and restrictions for federated identity credentials](workload-identity-federation-considerations.md)
+
+### Updated articles
+
+- [How to use Continuous Access Evaluation enabled APIs in your applications](app-resilience-continuous-access-evaluation.md)
+- [Run automated integration tests](test-automate-integration-testing.md)
+- [Tutorial: Sign in users and call the Microsoft Graph API from a JavaScript single-page application (SPA)](tutorial-v2-javascript-spa.md)
+
 ## August 2022
 
 ### Updated articles
@@ -51,13 +64,3 @@ Welcome to what's new in the Microsoft identity platform documentation. This art
 - [Microsoft identity platform access tokens](access-tokens.md)
 - [Single-page application: Sign-in and Sign-out](scenario-spa-sign-in.md)
 - [Tutorial: Add sign-in to Microsoft to an ASP.NET web app](tutorial-v2-asp-webapp.md)
-
-## June 2022
-
-### Updated articles
-
-- [Add app roles to your application and receive them in the token](howto-add-app-roles-in-azure-ad-apps.md)
-- [Azure AD Authentication and authorization error codes](reference-aadsts-error-codes.md)
-- [Microsoft identity platform refresh tokens](refresh-tokens.md)
-- [Single-page application: Acquire a token to call an API](scenario-spa-acquire-token.md)
-- [Tutorial: Sign in users and call the Microsoft Graph API in an Electron desktop app](tutorial-v2-nodejs-desktop.md)

articles/active-directory/manage-apps/whats-new-docs.md

@@ -1,7 +1,7 @@
 ---
 title: "What's new in Azure Active Directory application management"
 description: "New and updated documentation for the Azure Active Directory application management."
-ms.date: 09/06/2022
+ms.date: 10/03/2022
 ms.service: active-directory
 ms.subservice: app-mgmt
 ms.topic: reference
@@ -15,6 +15,18 @@ manager: CelesteDG
 
 Welcome to what's new in Azure Active Directory (Azure AD) application management documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the application management service, see [What's new in Azure AD](../fundamentals/whats-new.md).
 
+## September 2022
+
+### New articles
+
+- [Tutorial: Configure Datawiza to enable Azure Active Directory Multi-Factor Authentication and single sign-on to Oracle PeopleSoft](datawiza-azure-ad-sso-oracle-peoplesoft.md)
+- [SAML Request Signature Verification (Preview)](howto-enforce-signed-saml-authentication.md)
+
+### Updated articles
+
+- [Manage app consent policies](manage-app-consent-policies.md)
+- [Unexpected consent prompt when signing in to an application](application-sign-in-unexpected-user-consent-prompt.md)
+
 ## August 2022
 
 ### Updated articles
@@ -39,10 +51,3 @@ Welcome to what's new in Azure Active Directory (Azure AD) application managemen
 - [Configure Azure Active Directory SAML token encryption](howto-saml-token-encryption.md)
 - [Review permissions granted to applications](manage-application-permissions.md)
 - [Tutorial: Configure Secure Hybrid Access with Azure Active Directory and Datawiza](datawiza-with-azure-ad.md)
-
-## June 2022
-
-### Updated articles
-
-- [Protect against consent phishing](protect-against-consent-phishing.md)
-- [Request to publish your application in the Azure AD application gallery](v2-howto-app-gallery-listing.md)

articles/app-service/web-sites-monitor.md

@@ -56,16 +56,13 @@ You can increase or remove quotas from your app by upgrading your App Service pl
 
 ## Understand metrics
 
-> [!NOTE]
-> **File System Usage** is now available globally for apps hosted in multi-tenants and App Service Environment.
-> 
-
 > [!IMPORTANT]
 > **Average Response Time** will be deprecated to avoid confusion with metric aggregations. Use **Response Time** as a replacement.
 
 > [!NOTE]
 > Metrics for an app include the requests to the app's SCM site(Kudu).  This includes requests to view the site's logstream using Kudu.  Logstream requests may span several minutes, which will affect the Request Time metrics.  Users should be aware of this relationship when using these metrics with autoscale logic.
 > 
+> **Http Server Errors** only records requests that reach the backend service (the worker(s) hosting the app). If the requests are failing at the FrontEnd, they are not recorded as Http Server Errors. The [Health Check feature](./monitor-instances-health-check.md) / Application Insights availability tests can be used for outside in monitoring.
 
 Metrics provide information about the app or the App Service plan's behavior.
 

articles/azure-arc/kubernetes/cluster-connect.md

@@ -186,7 +186,7 @@ A conceptual overview of this feature is available in [Cluster connect - Azure A
     ```
 
     ```console
-    TOKEN=$(kubectl get secret demo-user-secret -o jsonpath='{$.data.token}' | base64 -d | sed 's/$/\\\n/g')
+    TOKEN=$(kubectl get secret demo-user-secret -o jsonpath='{$.data.token}' | base64 -d | sed 's/$/\n/g')
     ```
 1. Get the token to output to console
   

articles/azure-monitor/alerts/alerts-create-new-alert-rule.md

@@ -90,8 +90,8 @@ And then defining these elements for the resulting alert actions using:
         |Threshold value|If you selected a **static** threshold, enter the threshold value for the condition logic. |
         |Unit|If the selected metric signal supports different units,such as bytes, KB, MB, and GB, and if you selected a **static** threshold, enter the unit for the condition logic.|
         |Threshold sensitivity| If you selected a **dynamic** threshold, enter the sensitivity level. The sensitivity level affects the amount of deviation from the metric series pattern is required to trigger an alert. |
-        |Aggregation granularity| Select the interval over which data points are grouped using the aggregation type function.|
-        |Frequency of evaluation|Select the frequency on how often the alert rule should be run. Selecting frequency smaller than granularity of data points grouping will result in sliding window evaluation.  |
+        |Aggregation granularity| Select the interval that is used to group the data points using the aggregation type function. Choose an **Aggregation granularity** (Period) that's greater than the **Frequency of evaluation** to reduce the likelihood of missing the first evaluation period of an added time series.|
+        |Frequency of evaluation|Select how often the alert rule is be run. Select a frequency that is smaller than the aggregation granularity to generate a sliding window for the evaluation.|
 
     1. Select **Done**.
     ### [Log alert](#tab/log)

articles/azure-monitor/alerts/itsmc-definition.md

@@ -79,7 +79,7 @@ Action groups provide a modular and reusable way to trigger actions for your Azu
 
 ### Define a template
 
-Certain work item types can use templates that you define in ServiceNow. When you use templates, you can define fields that will be automatically populated by using constant values defined in ServiceNow (not values from the payload). The templates are synced with Azure. You can define which template you want to use as a part of the definition of an action group. For information about how to create templates, see the [ServiceNow documentation](https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/form-administration/task/t_CreateATemplateUsingTheTmplForm.html).
+Certain work item types can use templates that you define in ServiceNow. When you use templates, you can define fields that will be automatically populated by using constant values defined in ServiceNow (not values from the payload). The templates are synced with Azure. You can define which template you want to use as a part of the definition of an action group. For information about how to create templates, see the [ServiceNow documentation](https://www.servicenow.com/community/now-platform-articles/servicenow-versions/ta-p/2312014).
 
 To create an action group:
 
@@ -147,4 +147,4 @@ When you create or edit an Azure alert rule, use an action group, which has an I
 
 ## Next steps
 
-[Troubleshoot problems in ITSMC](./itsmc-resync-servicenow.md)
+[Troubleshoot problems in ITSMC](./itsmc-resync-servicenow.md)

articles/healthcare-apis/iot/deploy-02-new-button.md

@@ -0,0 +1,112 @@
+---
+title: Deploy the MedTech service with a QuickStart template - Azure Health Data Services
+description: In this article, you'll learn how to deploy the MedTech service in the Azure portal using a QuickStart template.
+author: mcevoy-building7
+ms.service: healthcare-apis
+ms.subservice: fhir
+ms.topic: quickstart
+ms.date: 09/30/2022
+ms.author: v-smcevoy
+---
+
+# Deploy the MedTech service with an Azure Resource Manager QuickStart template
+
+In this article, you'll learn how to deploy the MedTech service in the Azure portal using an Azure Resource Manager (ARM) Quickstart template. This template will be used with the **Deploy to Azure** button to make it easy to provide the information you need to automatically set up the infrastructure and configuration of your deployment. For more information about Azure ARM templates, see [What are ARM templates?](../../azure-resource-manager/templates/overview.md).
+
+If you need to see a diagram with information on the MedTech service deployment, there is an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resource (FHIR) Observation.
+
+There are four simple tasks you need to complete in order to deploy MedTech service with the ARM template **Deploy to Azure** button. They are:
+
+## Prerequisites
+
+In order to begin deployment, you need to have the following prerequisites:
+
+- An active Azure subscription account. If you don't have an Azure subscription, see [Subscription decision guide](/azure/cloud-adoption-framework/decision-guides/subscriptions/).
+
+- Two resource providers registered with your Azure subscription: **Microsoft.HealthcareApis** and **Microsoft.EventHub**. To learn more about registering resource providers, see [Azure resource providers and types](../../azure-resource-manager/management/resource-providers-and-types.md).
+
+When you've fulfilled these two prerequisites, you are ready to begin the second task.
+
+## Deploy to Azure button
+
+Next, you need to select the ARM template **Deploy to Azure** button here:
+
+ [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.healthcareapis%2Fworkspaces%2Fiotconnectors%2Fazuredeploy.json).
+
+This button will call a template from the Azure ARM QuickStart template library to get information from your Azure subscription environment and begin deploying the MedTech service.
+
+After you select the **Deploy to Azure** button, it may take a few minutes to implement the following resources and roles:
+
+- An Azure Event Hubs Namespace and device message Azure event hub. In this example, the event hub is named **devicedata**.
+
+- An Azure event hub consumer group. In this example, the consumer group is named **$Default**.
+
+- An Azure event hub sender role. In this example, the sender role is named **devicedatasender**.
+
+- An Azure Health Data Services workspace.
+
+- An Azure Health Data Services FHIR service.
+
+- An Azure Health Data Services MedTech service instance, including the necessary [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) roles to the device message event hub (named **Azure Events Hubs Receiver**) and FHIR service (named **FHIR Data Writer**).
+
+After these resources and roles have completed their implementation, the Azure portal will be launched.
+
+## Provide configuration details
+
+When the Azure portal screen appears, your next task is to fill out five fields that provide specific details of your deployment configuration.
+
+:::image type="content" source="media\iot-deploy-quickstart-in-portal\iot-deploy-quickstart-options.png" alt-text="Screenshot of Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\iot-deploy-quickstart-in-portal\iot-deploy-quickstart-options.png":::
+
+### Use these values to fill out the five fields
+
+- **Subscription** - Choose the Azure subscription you want to use for the deployment.
+
+- **Resource Group** - Choose an existing Resource Group or create a new Resource Group.
+
+- **Region** - The Azure region of the Resource Group used for the deployment. This field will auto-fill, based on the Resource Group region.
+
+- **Basename** - This value will be appended to the name of the Azure resources and services to be deployed.
+
+- **Location** - Use the drop-down list to select a supported Azure region for the Azure Health Data Services (the value could be the same or different region than your Resource Group).
+
+### When completed, do the following
+
+Don't change the **Device Mapping** and **Destination Mapping** default values at this time.
+
+Select the **Review + create** button after all the fields are filled out. This will review your input and check to see if all your values are valid.
+
+When the validation is successful, select the **Create** button to begin the deployment. After a brief wait, a message will appear telling you that your deployment is complete.
+
+## Required post-deployment tasks
+
+Now that the MedTech service is successfully deployed, there are three post-deployment tasks that need to be completed before MedTech is fully functional and ready for use:
+
+1. First, you must provide a working device mapping. For more information, see [How to use device mappings](how-to-use-device-mappings.md).
+
+2. Second, you need to ensure that you have a working FHIR destination mapping. For more information, see [How to use FHIR destination mappings](how-to-use-fhir-mappings.md).
+
+3. Third, you must use a Shared access policies (SAS) key (named **devicedatasender**) to connect your device or application to the MedTech service device message event hub (named **devicedata**). For more information, see [Connection string for a specific event hub in a namespace](../../event-hubs/event-hubs-get-connection-string.md#connection-string-for-a-specific-event-hub-in-a-namespace).
+
+> [!IMPORTANT]
+>
+> If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service has its own event hub consumer group. Consumer groups enable multiple consuming applications to each have a separate view of the event stream, and to read the stream independently at their own pace and with their own offsets. For more information, see [Consumer groups](../../event-hubs/event-hubs-features.md#consumer-groups).
+>
+> **Examples:**
+>
+> - Two MedTech services accessing the same device message event hub.
+> - A MedTech service and a storage writer application accessing the same device message event hub.
+
+## Next steps
+
+In this article, you learned how to deploy the MedTech service in the Azure portal using a Quickstart ARM template with a **Deploy to Azure** button. To learn more about other methods of deployment, see
+
+>[!div class="nextstepaction"]
+>[Choosing a method of deployment for MedTech service in Azure](deploy-iot-connector-in-azure.md)
+
+>[!div class="nextstepaction"]
+>[How to manually deploy MedTech service with Azure portal](deploy-03-new-manual.md)
+
+>[!div class="nextstepaction"]
+>[How to deploy MedTech service using an ARM template and Azure PowerShell or Azure CLI](deploy-08-new-ps-cli.md)
+
+FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.