Skip to content

Commit 0fad941

Browse files
authored
Merge pull request #107704 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
2 parents bbd90a2 + a221f62 commit 0fad941

16 files changed

+35
-32
lines changed

articles/aks/developer-best-practices-pod-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ This article focused on how to secure your pods. To implement some of these area
103103
* [Integrate Azure Key Vault with AKS][aks-keyvault-flexvol]
104104
105105
<!-- EXTERNAL LINKS -->
106-
[aad-pod-identity]: https://github.com/Azure/aad-pod-identity#demo-pod
106+
[aad-pod-identity]: https://github.com/Azure/aad-pod-identity#demo
107107
[aks-keyvault-flexvol]: https://github.com/Azure/kubernetes-keyvault-flexvol
108108
[linux-capabilities]: http://man7.org/linux/man-pages/man7/capabilities.7.html
109109
[selinux-labels]: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.12/#selinuxoptions-v1-core

articles/aks/windows-node-limitations.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,7 @@ title: Limitations for Windows Server node pools in Azure Kubernetes Service (AK
33
description: Learn about the known limitations when you run Windows Server node pools and application workloads in Azure Kubernetes Service (AKS)
44
services: container-service
55
ms.topic: article
6-
ms.date: 05/31/2019
7-
6+
ms.date: 12/18/2019
87

98
#Customer intent: As a cluster operator, I want to understand the current limitations when running Windows node pools and application workloads.
109
---

articles/app-service/app-service-ip-restrictions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The list will show all of the current restrictions that are on your app. If you
3838

3939
## Adding IP address rules
4040

41-
You can click on **[+] Add** to add a new access restriction rule. Once you add a rule, it will become effective immediately. Rules are enforced in priority order starting from the lowest number and going up. There is an implicit deny all that is in effect once you add even a single rule.
41+
You can click on **[+] Add rule** to add a new access restriction rule. Once you add a rule, it will become effective immediately. Rules are enforced in priority order starting from the lowest number and going up. There is an implicit deny all that is in effect once you add even a single rule.
4242

4343
When creating a rule, you must select allow/deny and also the type of rule. You are also required to provide the priority value and what you are restricting access to. You can optionally add a name, and description to the rule.
4444

@@ -66,13 +66,13 @@ When you edit a rule, you cannot change the type between an IP address rule and
6666

6767
![edit an access restriction rule](media/app-service-ip-restrictions/access-restrictions-vnet-edit.png)
6868

69-
To delete a rule, click the **...** on your rule and then click **remove**.
69+
To delete a rule, click the **...** on your rule and then click **Remove**.
7070

7171
![delete access restriction rule](media/app-service-ip-restrictions/access-restrictions-delete.png)
7272

7373
## Blocking a single IP Address ##
7474

75-
When adding your first IP Restriction rule, the service will add an explicit **deny all** rule with a priority of 2147483647. In practice, the explicit **deny all** rule will be last rule executed and will block access to any IP address that is not explicitly allowed using an **Allow** rule.
75+
When adding your first IP Restriction rule, the service will add an explicit **Deny all** rule with a priority of 2147483647. In practice, the explicit **Deny all** rule will be last rule executed and will block access to any IP address that is not explicitly allowed using an **Allow** rule.
7676

7777
For the scenario where users want to explicitly block a single IP address or IP address block, but allow everything else access, it is necessary to add an explicit **Allow All** rule.
7878

@@ -124,7 +124,7 @@ The JSON syntax for the earlier example is:
124124

125125
## Azure Function App Access Restrictions
126126

127-
Access restrictions are available for both Function Apps with the same functionality as App Service plans. Enabling access restrictions will disable the portal code editor for any disallowed IPs.
127+
Access restrictions are also available for Function Apps with the same functionality as App Service plans. Enabling access restrictions will disable the portal code editor for any disallowed IPs.
128128

129129
## Next steps
130130
[Access restrictions for Azure Function Apps](../azure-functions/functions-networking-options.md#inbound-ip-restrictions)

articles/application-gateway/ingress-controller-install-new.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -134,15 +134,15 @@ To install AAD Pod Identity to your cluster:
134134
135135
- *RBAC enabled* AKS cluster
136136
137-
```bash
138-
kubectl create -f https://raw.githubusercontent.com/Azure/aad-pod-identity/master/deploy/infra/deployment-rbac.yaml
139-
```
137+
```bash
138+
kubectl create -f https://raw.githubusercontent.com/Azure/aad-pod-identity/master/deploy/infra/deployment-rbac.yaml
139+
```
140140
141141
- *RBAC disabled* AKS cluster
142142
143-
```bash
144-
kubectl create -f https://raw.githubusercontent.com/Azure/aad-pod-identity/master/deploy/infra/deployment.yaml
145-
```
143+
```bash
144+
kubectl create -f https://raw.githubusercontent.com/Azure/aad-pod-identity/master/deploy/infra/deployment.yaml
145+
```
146146
147147
### Install Helm
148148
[Helm](https://docs.microsoft.com/azure/aks/kubernetes-helm) is a package manager for

articles/azure-monitor/platform/template-workspace-configuration.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ The deployment can take a few minutes to complete. When it finishes, you see a m
173173
The following template sample illustrates how to:
174174

175175
1. Add solutions to the workspace
176-
2. Create saved searches
176+
2. Create saved searches. To ensure that deployments don't override saved searches accidently, an eTag property should be added in the "savedSearches" resource to override and maintain the idempotency of saved searches.
177177
3. Create a computer group
178178
4. Enable collection of IIS logs from computers with the Windows agent installed
179179
5. Collect Logical Disk perf counters from Linux computers (% Used Inodes; Free Megabytes; % Used Space; Disk Transfers/sec; Disk Reads/sec; Disk Writes/sec)
@@ -315,11 +315,11 @@ The following template sample illustrates how to:
315315
"[concat('Microsoft.OperationalInsights/workspaces/', parameters('workspaceName'))]"
316316
],
317317
"properties": {
318-
"Category": "VMSS",
319-
"ETag": "*",
320-
"DisplayName": "VMSS Instance Count",
321-
"Query": "Event | where Source == \"ServiceFabricNodeBootstrapAgent\" | summarize AggregatedValue = count() by Computer",
322-
"Version": 1
318+
"category": "VMSS",
319+
"eTag": "*",
320+
"displayName": "VMSS Instance Count",
321+
"query": "Event | where Source == \"ServiceFabricNodeBootstrapAgent\" | summarize AggregatedValue = count() by Computer",
322+
"version": 1
323323
}
324324
},
325325
{

articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: conceptual
77
ms.date: 10/04/2018
88
ms.author: tomfitz
99
---
10-
# Deploy service catalog app through Azure portal
10+
# Quickstart: Deploy service catalog app through Azure portal
1111

1212
In the [preceding quickstart](publish-managed-app-definition-quickstart.md), you published a managed application definition. In this quickstart, you create a service catalog app from that definition.
1313

@@ -59,4 +59,4 @@ After the service catalog app has been deployed, you have two new resource group
5959

6060
* To learn how to create the definition files for a managed application, see [Create and publish a managed application definition](publish-service-catalog-app.md).
6161
* For Azure CLI, see [Deploy service catalog app with Azure CLI](./scripts/managed-application-cli-sample-create-application.md).
62-
* For PowerShell, see [Deploy service catalog app with PowerShell](./scripts/managed-application-poweshell-sample-create-application.md).
62+
* For PowerShell, see [Deploy service catalog app with PowerShell](./scripts/managed-application-poweshell-sample-create-application.md).

articles/azure-resource-manager/managed-applications/publish-managed-app-definition-quickstart.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: quickstart
77
ms.date: 09/13/2019
88
ms.author: tomfitz
99
---
10-
# Publish an Azure managed application definition
10+
# Quickstart: Publish an Azure managed application definition
1111

1212
This quickstart provides an introduction to working with managed applications. You add a managed application definition to an internal catalog for users in your organization. To simplify the introduction, we have already built the files for your managed application. Those files are available through GitHub. You learn how to build those files in the [Create service catalog application](publish-service-catalog-app.md) tutorial.
1313

@@ -69,4 +69,4 @@ Some of the parameters used in the preceding example are:
6969
You've published the managed application definition. Now, learn how to deploy an instance of that definition.
7070

7171
> [!div class="nextstepaction"]
72-
> [Quickstart: Deploy service catalog app](deploy-service-catalog-quickstart.md)
72+
> [Quickstart: Deploy service catalog app](deploy-service-catalog-quickstart.md)

articles/azure-resource-manager/managed-applications/publish-marketplace-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 07/17/2019
88
ms.author: tomfitz
99
---
1010

11-
# Azure managed applications in the Marketplace
11+
# Tutorial: Publish Azure managed applications in the Marketplace
1212

1313
Vendors can use Azure managed applications to offer their solutions to all Azure Marketplace customers. Those vendors can include managed service providers (MSPs), independent software vendors (ISVs), and system integrators (SIs). Managed applications reduce the maintenance and servicing overhead for customers. Vendors sell infrastructure and software through the marketplace. They can attach services and operational support to managed applications. For more information, see [Managed application overview](overview.md).
1414

articles/azure-resource-manager/managed-applications/publish-service-catalog-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: tutorial
77
ms.date: 10/04/2018
88
ms.author: tomfitz
99
---
10-
# Create and publish a managed application definition
10+
# Tutorial: Create and publish a managed application definition
1111

1212
[!INCLUDE [updated-for-az](../../../includes/updated-for-az.md)]
1313

articles/cognitive-services/Bing-Custom-Search/includes/quickstarts/custom-search-client-library-csharp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ Use the Bing Custom Search client library for C# to:
8181
{
8282
Console.WriteLine("Didn't see any Web data..");
8383
}
84-
```csharp
84+
```
8585

8686
## Next steps
8787

0 commit comments

Comments
 (0)