Merge pull request #95170 from MicrosoftDocs/master

11/07 AM Publish

Author: huypub

articles/active-directory/b2b/troubleshoot.md

@@ -1,18 +1,19 @@
 ---
 title: Troubleshooting B2B collaboration - Azure Active Directory | Microsoft Docs
 description: Remedies for common problems with Azure Active Directory B2B collaboration
-
 services: active-directory
 ms.service: active-directory
 ms.subservice: B2B
-ms.topic: conceptual
+ms.topic: troubleshooting
 ms.date: 05/25/2017
-
+tags: active-directory
 ms.author: mimart
 author: v-miegge
-manager: celestedg
+manager: dcscontentpm
 ms.reviewer: mal
-ms.custom: "it-pro, seo-update-azuread-jan"
+ms.custom:
+  - it-pro
+  - seo-update-azuread-jan"
 ms.collection: M365-identity-device-management
 ---
 

articles/active-directory/develop/quickstart-v2-javascript.md

@@ -79,12 +79,11 @@ Select the option that's suitable to your development environment:
 
 * (Optional) To run the project with the IIS server, [download the Visual Studio project](https://github.com/Azure-Samples/active-directory-javascript-graphapi-v2/archive/vsquickstart.zip). Extract the zip file to a local folder (for example, *C:\Azure-Samples*).
 
-#### Step 3: Configure your JavaScript app
-
 > [!div renderon="docs"]
+> #### Step 3: Configure your JavaScript app
 > In the *JavaScriptSPA* folder, edit *index.html*, and set the `clientID` and `authority` values under `msalConfig`.
 
-> [!div class="sxs-lookup" renderon="portal"]
+> [!div renderon="docs"]
 > In the *JavaScriptSPA* folder, edit *index.html*, and replace `msalConfig` with the following code:
 
 ```javascript
@@ -101,10 +100,6 @@ var msalConfig = {
 };
 
 ```
-> [!div renderon="portal"]
-> > [!NOTE]
-> > This quickstart supports Enter_the_Supported_Account_Info_Here.
-
 
 > [!div renderon="docs"]
 >
@@ -119,7 +114,12 @@ var msalConfig = {
 > > To find the values of **Application (client) ID**, **Directory (tenant) ID**, and **Supported account types**, go to the app's **Overview** page in the Azure portal.
 >
 
-#### Step 4: Run the project
+> [!div class="sxs-lookup" renderon="portal"]
+> #### Step 3: Your app is configured and ready to run
+> We have configured your project with values of your app's properties. 
+
+> [!div renderon="docs"]
+> #### Step 4: Run the project
 
 * If you're using [Node.js](https://nodejs.org/en/download/):
 

articles/active-directory/manage-apps/application-proxy-integrate-with-power-bi.md

@@ -78,7 +78,7 @@ For more information, see [Kerberos Constrained Delegation for single sign-on to
 Now you're ready to configure Azure AD Application Proxy.
 
 1. Publish Report Services through Application Proxy with the following settings. For step-by-step instructions on how to publish an application through Application Proxy, see [Publishing applications using Azure AD Application Proxy](application-proxy-add-on-premises-application.md#add-an-on-premises-app-to-azure-ad).
-   - **Internal URL**: Enter the URL to the Report Server that the connector can reach in the corporate network. Make sure this URL is reachable from the server the connector is installed on. A best practice is using a top-level domain such as `https://servername/` to avoid issues with subpaths (for example, `https://servername/reports/` and `https://servername/reportserver/`) not published through Application Proxy.
+   - **Internal URL**: Enter the URL to the Report Server that the connector can reach in the corporate network. Make sure this URL is reachable from the server the connector is installed on. A best practice is using a top-level domain such as `https://servername/` to avoid issues with subpaths published through Application Proxy. For example, use `https://servername/` and not `https://servername/reports/` or `https://servername/reportserver/`.
      > [!NOTE]
      > We recommend using a secure HTTPS connection to the Report Server. See [Configure SSL connections on a native mode report server](https://docs.microsoft.com/sql/reporting-services/security/configure-ssl-connections-on-a-native-mode-report-server?view=sql-server-2017) for information how to.
    - **External URL**: Enter the public URL the Power BI mobile app will connect to. For example, it may look like `https://reports.contoso.com` if a custom domain is used. To use a custom domain, upload a certificate for the domain, and point a DNS record to the default msappproxy.net domain for your application. For detailed steps, see [Working with custom domains in Azure AD Application Proxy](application-proxy-configure-custom-domain.md).

articles/aks/coredns-custom.md

@@ -47,7 +47,7 @@ data:
         errors
         cache 30
         rewrite name substring <domain to be rewritten>.com default.svc.cluster.local
-        proxy .  /etc/resolv.conf # you can redirect this to a specific DNS server such as 10.0.0.10
+        forward .  /etc/resolv.conf # you can redirect this to a specific DNS server such as 10.0.0.10
     }
 ```
 
@@ -72,9 +72,9 @@ kubectl delete pod --namespace kube-system -l k8s-app=kube-dns
 > [!Note]
 > The command above is correct. While we're changing `coredns`, the deployment is under the **kube-dns** name.
 
-## Custom proxy server
+## Custom forward server
 
-If you need to specify a proxy server for your network traffic, you can create a ConfigMap to customize DNS. In the following example, update the `proxy` name and address with the values for your own environment. Create a file named `corednsms.yaml` and paste the following example configuration:
+If you need to specify a forward server for your network traffic, you can create a ConfigMap to customize DNS. In the following example, update the `forward` name and address with the values for your own environment. Create a file named `corednsms.yaml` and paste the following example configuration:
 
 ```yaml
 apiVersion: v1
@@ -85,15 +85,15 @@ metadata:
 data:
   test.server: | # you may select any name here, but it must end with the .server file extension
     <domain to be rewritten>.com:53 {
-        proxy foo.com 1.1.1.1
+        forward foo.com 1.1.1.1
     }
 ```
 
 As in the previous examples, create the ConfigMap using the [kubectl apply configmap][kubectl-apply] command and specify the name of your YAML manifest. Then, force CoreDNS to reload the ConfigMap using the [kubectl delete pod][kubectl delete] for the Kubernetes Scheduler to recreate them:
 
 ```console
 kubectl apply -f corednsms.yaml
-kubectl delete pod --namespace kube-system --label k8s-app=kube-dns
+kubectl delete pod --namespace kube-system --selector k8s-app=kube-dns
 ```
 
 ## Use custom domains
@@ -113,15 +113,15 @@ data:
     puglife.local:53 {
         errors
         cache 30
-        proxy . 192.11.0.1  # this is my test/dev DNS server
+        forward . 192.11.0.1  # this is my test/dev DNS server
     }
 ```
 
 As in the previous examples, create the ConfigMap using the [kubectl apply configmap][kubectl-apply] command and specify the name of your YAML manifest. Then, force CoreDNS to reload the ConfigMap using the [kubectl delete pod][kubectl delete] for the Kubernetes Scheduler to recreate them:
 
 ```console
 kubectl apply -f corednsms.yaml
-kubectl delete pod --namespace kube-system --label k8s-app=kube-dns
+kubectl delete pod --namespace kube-system --selector k8s-app=kube-dns
 ```
 
 ## Stub domains
@@ -139,12 +139,12 @@ data:
     abc.com:53 {
         errors
         cache 30
-        proxy . 1.2.3.4
+        forward . 1.2.3.4
     }
     my.cluster.local:53 {
         errors
         cache 30
-        proxy . 2.3.4.5
+        forward . 2.3.4.5
     }
 
 ```
@@ -153,7 +153,7 @@ As in the previous examples, create the ConfigMap using the [kubectl apply confi
 
 ```console
 kubectl apply -f corednsms.yaml
-kubectl delete pod --namespace kube-system --label k8s-app=kube-dns
+kubectl delete pod --namespace kube-system --selector k8s-app=kube-dns
 ```
 
 ## Hosts plugin
@@ -185,8 +185,6 @@ To learn more about core network concepts, see [Network concepts for application
 [coredns]: https://coredns.io/
 [corednsk8s]: https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/#coredns
 [dnscache]: https://coredns.io/plugins/cache/
-[aks-quickstart-cli]: https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough
-[aks-quickstart-portal]: https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough-portal
 [kubectl-apply]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#apply
 [kubectl-get]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#get
 [kubectl delete]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#delete

articles/api-management/api-management-api-import-restrictions.md

@@ -12,7 +12,7 @@ ms.service: api-management
 ms.workload: mobile
 ms.tgt_pltfrm: na
 ms.topic: article
-ms.date: 06/26/2019
+ms.date: 11/06/2019
 ms.author: apimpm
 ---
 
@@ -36,6 +36,8 @@ If you're receiving errors importing your OpenAPI document, make sure you've val
 -   Source file URL (if available) is applied to relative server URLs.
 -   Security definitions are ignored.
 -   Inline schema definitions for API operations are not supported. Schema definitions are defined in the API scope and can be referenced in API operations request or response scopes.
+-   A defined URL parameter needs to be part of the URL template.
+-   **Produces** keyword, which describes MIME types returned by an API, is not supported. 
 
 ### <a name="open-api-v2"> </a>OpenAPI version 2
 

articles/api-management/api-management-howto-developer-portal.md

@@ -113,7 +113,31 @@ No.
 
 ### I'm getting a CORS error when using the interactive console. What should I do?
 
-The interactive console makes a client-side API request from the browser. You can resolve the CORS problem by adding [a CORS policy](https://docs.microsoft.com/azure/api-management/api-management-cross-domain-policies#CORS) on your API(s). You can either specify all the parameters manually (for example, origin as https://contoso.com) or use a wildcard `*` value.
+The interactive console makes a client-side API request from the browser. You can resolve the CORS problem by adding [a CORS policy](https://docs.microsoft.com/azure/api-management/api-management-cross-domain-policies#CORS) on your API(s). You can specify all the parameters manually or use wildcard `*` values. For example:
+
+```XML
+<cors>
+    <allowed-origins>
+        <origin>*</origin>
+    </allowed-origins>
+    <allowed-methods>
+        <method>GET</method>
+        <method>POST</method>
+        <method>PUT</method>
+        <method>DELETE</method>
+        <method>HEAD</method>
+        <method>OPTIONS</method>
+        <method>PATCH</method>
+        <method>TRACE</method>
+    </allowed-methods>
+    <allowed-headers>
+        <header>*</header>
+    </allowed-headers>
+    <expose-headers>
+        <header>*</header>
+    </expose-headers>
+</cors>
+```
 
 ## Next steps
 

articles/application-gateway/ingress-controller-add-health-probes.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: caya
 ms.service: application-gateway
 ms.topic: article
-ms.date: 10/23/2019
+ms.date: 11/4/2019
 ms.author: caya
 ---
 

articles/application-gateway/ingress-controller-annotations.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: caya
 ms.service: application-gateway
 ms.topic: article
-ms.date: 10/11/2019
+ms.date: 11/4/2019
 ms.author: caya
 ---
 

articles/application-gateway/ingress-controller-autoscale-pods.md

@@ -0,0 +1,120 @@
+---
+title: Autoscale AKS pods with Azure Application Gateway metrics
+description: This article provides instructions on how to scale your AKS backend pods using Application Gateway metrics and Azure Kubernetes Metric Adapter
+services: application-gateway
+author: caya
+ms.service: application-gateway
+ms.topic: article
+ms.date: 11/4/2019
+ms.author: caya
+---
+
+# Autoscale your AKS pods using Application Gateway Metrics (Beta)
+
+As incoming traffic increases, it becomes crucial to scale up your applications based on the demand.
+
+In the following tutorial, we explain how you can use Application Gateway's `AvgRequestCountPerHealthyHost` metric to scale up your application. `AvgRequestCountPerHealthyHost` measures average requests sent to a specific backend pool and backend HTTP setting combination.
+
+We are going to use following two components:
+
+* [`Azure Kubernetes Metric Adapter`](https://github.com/Azure/azure-k8s-metrics-adapter) - We will use the metric adapter to expose Application Gateway metrics through the metric server. The Azure Kubernetes Metric Adapter is an open source project under Azure, similar to the Application Gateway Ingress Controller. 
+* [`Horizontal Pod Autoscaler`](https://docs.microsoft.com/azure/aks/concepts-scale#horizontal-pod-autoscaler) - We will use HPA to use Application Gateway metrics and target a deployment for scaling.
+
+## Setting up Azure Kubernetes Metric Adapter
+
+1. We will first create an Azure AAD service principal and assign it `Monitoring Reader` access over Application Gateway's resource group. 
+
+    ```bash
+        applicationGatewayGroupName="<application-gateway-group-id>"
+        applicationGatewayGroupId=$(az group show -g $applicationGatewayGroupName -o tsv --query "id")
+        az ad sp create-for-rbac -n "azure-k8s-metric-adapter-sp" --role "Monitoring Reader" --scopes applicationGatewayGroupId
+    ```
+
+1. Now, We will deploy the [`Azure Kubernetes Metric Adapter`](https://github.com/Azure/azure-k8s-metrics-adapter) using the AAD service principal created above.
+
+    ```bash
+    kubectl create namespace custom-metrics
+    # use values from service principle created above to create secret
+    kubectl create secret generic azure-k8s-metrics-adapter -n custom-metrics \
+        --from-literal=azure-tenant-id=<tenantid> \
+        --from-literal=azure-client-id=<clientid> \
+        --from-literal=azure-client-secret=<secret>
+    kubectl apply -f kubectl apply -f https://raw.githubusercontent.com/Azure/azure-k8s-metrics-adapter/master/deploy/adapter.yaml -n custom-metrics
+    ```
+
+1. We will create an `ExternalMetric` resource with name `appgw-request-count-metric`. This resource will instruct the metric adapter to expose `AvgRequestCountPerHealthyHost` metric for `myApplicationGateway` resource in `myResourceGroup` resource group. You can use the `filter` field to target a specific backend pool and backend HTTP setting in the Application Gateway.
+
+    ```yaml
+    apiVersion: azure.com/v1alpha2
+    kind: ExternalMetric
+    metadata:
+    name: appgw-request-count-metric
+    spec:
+        type: azuremonitor
+        azure:
+            resourceGroup: myResourceGroup # replace with your application gateway's resource group name
+            resourceName: myApplicationGateway # replace with your application gateway's name
+            resourceProviderNamespace: Microsoft.Network
+            resourceType: applicationGateways
+        metric:
+            metricName: AvgRequestCountPerHealthyHost
+            aggregation: Average
+            filter: BackendSettingsPool eq '<backend-pool-name>~<backend-http-setting-name>' # optional
+    ```
+
+You can now make a request to the metric server to see if our new metric is getting exposed:
+```bash
+kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1/namespaces/default/appgw-request-count-metric"
+# Sample Output
+# {
+#   "kind": "ExternalMetricValueList",
+#   "apiVersion": "external.metrics.k8s.io/v1beta1",
+#   "metadata":
+#     {
+#       "selfLink": "/apis/external.metrics.k8s.io/v1beta1/namespaces/default/appgw-request-count-metric",
+#     },
+#   "items":
+#     [
+#       {
+#         "metricName": "appgw-request-count-metric",
+#         "metricLabels": null,
+#         "timestamp": "2019-11-05T00:18:51Z",
+#         "value": "30",
+#       },
+#     ],
+# }
+```
+
+## Using the new metric to scale up the deployment
+
+Once we are able to expose `appgw-request-count-metric` through the metric server, we are ready to use [`Horizontal Pod Autoscaler`](https://docs.microsoft.com/azure/aks/concepts-scale#horizontal-pod-autoscaler) to scale up our target deployment.
+
+In following example, we will target a sample deployment `aspnet`. We will scale up Pods when `appgw-request-count-metric` > 200 per Pod upto a max of `10` Pods.
+
+Replace your target deployment name and apply the following auto scale configuration:
+```yaml
+apiVersion: autoscaling/v2beta1
+kind: HorizontalPodAutoscaler
+metadata:
+  name: deployment-scaler
+spec:
+  scaleTargetRef:
+    apiVersion: extensions/v1beta1
+    kind: Deployment
+    name: aspnet # replace with your deployment's name
+  minReplicas: 1
+  maxReplicas: 10
+  metrics:
+  - type: External
+    external:
+      metricName: appgw-request-count-metric
+      targetAverageValue: 200
+```
+
+Test your setup by using a load test tool like apache bench:
+```bash
+ab -n10000 http://<applicaiton-gateway-ip-address>/
+```
+
+## Next steps
+- [**Troubleshoot Ingress Controller issues**](ingress-controller-troubleshoot.md): Troubleshoot any issues with the Ingress Controller.

articles/application-gateway/ingress-controller-cookie-affinity.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: caya
 ms.service: application-gateway
 ms.topic: article
-ms.date: 10/23/2019
+ms.date: 11/4/2019
 ms.author: caya
 ---