Skip to content

Commit 9858ab6

Browse files
Merge pull request #91623 from MicrosoftDocs/master
Merge master to live, 4:25 AM
2 parents bd4198a + 1295bca commit 9858ab6

File tree

9 files changed

+36
-24
lines changed

9 files changed

+36
-24
lines changed

articles/active-directory/authentication/concept-authentication-passwordless.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ A security key **MUST** implement the following features and extensions from the
5252
| 3 | hmac-secret | This extension ensures you can sign in to your device when it's off-line or in airplane mode. |
5353
| 4 | Multiple accounts per RP | This feature ensures you can use the same security key across multiple services like Microsoft Account and Azure Active Directory. |
5454

55-
The following providers offer FIDO2 security keys of different form factors that are known to be compatible with the paswordless experience. Microsoft encourages customers to evaluate the security properties of these keys by contacting the vendor as well as FIDO Alliance.
55+
The following providers offer FIDO2 security keys of different form factors that are known to be compatible with the passwordless experience. Microsoft encourages customers to evaluate the security properties of these keys by contacting the vendor as well as FIDO Alliance.
5656

5757
| Provider | Contact |
5858
| --- | --- |

articles/app-service/webjobs-create.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
11
---
22
title: Run Background tasks with WebJobs - Azure App Service
33
description: Learn how to use WebJobs to run background tasks in Azure App Service web apps, API apps, or mobile apps.
4-
services: app-service
54
author: ggailey777
6-
manager: jeconnoc
7-
editor: jimbe
8-
ms.assetid: af01771e-54eb-4aea-af5f-f883ff39572b
5+
manager: wgallace
6+
s.assetid: af01771e-54eb-4aea-af5f-f883ff39572b
97
ms.service: app-service
10-
ms.topic: article
8+
ms.topic: conceptual
119
ms.date: 10/16/2018
1210
ms.author: glenga
1311
ms.reviewer: msangapu;david.ebbo;suwatch;pbatum;naren.soni
@@ -18,14 +16,14 @@ ms.custom: seodec18
1816

1917
# Run Background tasks with WebJobs in Azure App Service
2018

19+
This article shows how to deploy WebJobs by using the [Azure portal](https://portal.azure.com) to upload an executable or script. For information about how to develop and deploy WebJobs by using Visual Studio, see [Deploy WebJobs using Visual Studio](webjobs-dotnet-deploy-vs.md).
20+
2121
## Overview
22-
WebJobs is a feature of [Azure App Service](https://docs.microsoft.com/azure/app-service/) that enables you to run a program or script in the same context as a web app, API app, or mobile app. There is no additional cost to use WebJobs.
22+
WebJobs is a feature of [Azure App Service](index.yml) that enables you to run a program or script in the same context as a web app, API app, or mobile app. There is no additional cost to use WebJobs.
2323

2424
> [!IMPORTANT]
2525
> WebJobs is not yet supported for App Service on Linux.
2626
27-
This article shows how to deploy WebJobs by using the [Azure portal](https://portal.azure.com) to upload an executable or script. For information about how to develop and deploy WebJobs by using Visual Studio, see [Deploy WebJobs using Visual Studio](webjobs-dotnet-deploy-vs.md).
28-
2927
The Azure WebJobs SDK can be used with WebJobs to simplify many programming tasks. For more information, see [What is the WebJobs SDK](https://github.com/Azure/azure-webjobs-sdk/wiki).
3028

3129
Azure Functions provides another way to run programs and scripts. For a comparison between WebJobs and Functions, see [Choose between Flow, Logic Apps, Functions, and WebJobs](../azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md).
@@ -178,6 +176,8 @@ You can enter a [NCRONTAB expression](../azure-functions/functions-bindings-time
178176

179177
To learn more, see [Scheduling a triggered WebJob](webjobs-dotnet-deploy-vs.md#scheduling-a-triggered-webjob).
180178

179+
[!INCLUDE [webjobs-cron-timezone-note](../../includes/webjobs-cron-timezone-note.md)]
180+
181181
## <a name="ViewJobHistory"></a> View the job history
182182

183183
1. Select the WebJob you want to see history for, and then select the **Logs** button.

articles/app-service/webjobs-dotnet-deploy-vs.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,12 @@
11
---
22
title: Develop and deploy WebJobs using Visual Studio - Azure
33
description: Learn how to develop and deploy Azure WebJobs to Azure App Service using Visual Studio.
4-
services: app-service
5-
documentationcenter: ''
64
author: ggailey777
7-
manager: jeconnoc
8-
5+
manager: gwallace
96
ms.assetid: a3a9d320-1201-4ac8-9398-b4c9535ba755
107
ms.service: app-service
11-
ms.devlang: dotnet
12-
ms.topic: article
13-
ms.tgt_pltfrm: na
8+
ms.topic: conceptual
149
ms.custom: vs-azure
15-
ms.workload: azure-vs
1610
ms.date: 02/18/2019
1711
ms.author: glenga
1812
ms.reviewer: david.ebbo;suwatch;pbatum;naren.soni
@@ -227,6 +221,8 @@ When you [create a WebJob from the Azure portal](webjobs-create.md), the setting
227221

228222
WebJobs uses the same CRON expressions for scheduling as the timer trigger in Azure Functions. To learn more about CRON support, see the [timer trigger reference article](../azure-functions/functions-bindings-timer.md#ncrontab-expressions).
229223

224+
[!INCLUDE [webjobs-cron-timezone-note](../../includes/webjobs-cron-timezone-note.md)]
225+
230226
### setting.job reference
231227

232228
The following settings are supported by WebJobs:

articles/azure-maps/tutorial-search-location.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ This section shows how to use the Maps [Search API](https://docs.microsoft.com/r
215215
4. You can see the raw data that the map is rendering by entering the following HTTPRequest in your browser. Replace \<Your Azure Maps Key\> with your primary key.
216216

217217
```http
218-
https://atlas.microsoft.com/search/poi/json?api-version=2&query=gasoline%20station&subscription-key=<subscription-key>&lat=47.6292&lon=-122.2337&radius=100000
218+
https://atlas.microsoft.com/search/poi/json?api-version=1.0&query=gasoline%20station&subscription-key=<subscription-key>&lat=47.6292&lon=-122.2337&radius=100000
219219
```
220220

221221
At this point, the MapSearch page can display the locations of points of interest that are returned from a fuzzy search query. Let's add some interactive capabilities and more information about the locations.

articles/azure-monitor/insights/network-performance-monitor.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,7 @@ NPM can monitor connectivity between networks and applications in any part of th
4747
* South UK
4848
* Central India
4949
* US Government Virginia
50+
* China East 2
5051

5152

5253
The list of supported regions for ExpressRoute Monitor is available in the [documentation](https://docs.microsoft.com/azure/expressroute/how-to-npm?utm_swu=8117).

articles/frontdoor/waf-front-door-rate-limit-powershell.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -74,9 +74,7 @@ In the following example, the limit is set to 1000. Requests from any client to
7474

7575
Find the name of the resource group that contains the Front Door profile using `Get-AzureRmResourceGroup`. Next, configure a security policy with a custom rate limit rule using [New-AzFrontDoorWafPolicy](/powershell/module/az.frontdoor/new-azfrontdoorwafpolicy) in the specified resource group that contains the Front Door profile.
7676

77-
The below example uses the Resource Group name *myResourceGroupFD1* with the assumption that you have created the Front Door profile using instructions provided in the [Quickstart: Create a Front Door](quickstart-create-front-door.md) article.
78-
79-
using [New-AzFrontDoorWafPolicy](/powershell/module/az.frontdoor/new-azfrontdoorwafpolicy).
77+
The below example uses the Resource Group name *myResourceGroupFD1* with the assumption that you have created the Front Door profile using instructions provided in the [Quickstart: Create a Front Door](quickstart-create-front-door.md) article using [New-AzFrontDoorWafPolicy](/powershell/module/az.frontdoor/new-azfrontdoorwafpolicy).
8078

8179
```powershell-interactive
8280
$ratePolicy = New-AzFrontDoorWafPolicy `

articles/service-fabric/service-fabric-application-scenarios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Here's an example application that uses stateless services:
7070
![Application that uses stateless services][Image1]
7171

7272
Here's an example application that uses stateful services:
73-
![Application that uses stateless services][Image2]
73+
![Application that uses stateful services][Image2]
7474

7575
## Next steps
7676

articles/virtual-machines/workloads/sap/hana-network-architecture.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,14 @@ By default deployment, three network routing considerations are important for SA
135135
* SAP HANA on Azure (Large Instances) units have an assigned IP address from the server IP pool address range that you submitted when requesting the HANA Large Instance deployment. For more information, see [SAP HANA (Large Instances) infrastructure and connectivity on Azure](hana-overview-infrastructure-connectivity.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json). This IP address is accessible through the Azure subscriptions and circuit that connects Azure virtual networks to HANA Large Instances. The IP address assigned out of that server IP pool address range is directly assigned to the hardware unit. It's *not* assigned through NAT anymore, as was the case in the first deployments of this solution.
136136

137137
### Direct Routing to HANA Large Instances
138-
By default the transitive routing between HANA Large Instance units and on-premise or between HANA Large Instance routing that are deployed in two different regions does not work. There are several possibilities to enable such a transitive routing.
138+
139+
By default, the transitive routing does not work in these scenarios:
140+
141+
* Between HANA Large Instance units and an on-premises deployment.
142+
143+
* Between HANA Large Instance routing that are deployed in two different regions.
144+
145+
There are three ways to enable transitive routing in those scenarios:
139146

140147
- A reverse-proxy to route data, to and from. For example, F5 BIG-IP, NGINX with Traffic Manager deployed in the Azure virtual network that connects to HANA Large Instances and to on-premise as a virtual firewall/traffic routing solution.
141148
- Using [IPTables rules](http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_%3a_Ch14_%3a_Linux_Firewalls_Using_iptables#.Wkv6tI3rtaQ) in a Linux VM to enable routing between on-premises locations and HANA Large Instance units, or between HANA Large Instance units in different regions. The VM running IPTables needs to be deployed in the Azure virtual network that connects to HANA Large Instances and to on-premise. The VM needs to be sized accordingly, so, that the network throughput of the VM is sufficient for the expected network traffic. For details on VM network bandwidth, check the article [Sizes of Linux virtual machines in Azure](https://docs.microsoft.com/azure/virtual-machines/linux/sizes?toc=%2fazure%2fvirtual-network%2ftoc.json).
@@ -190,4 +197,4 @@ The figure shows how the different virtual networks in both regions are connecte
190197
> If you used multiple ExpressRoute circuits, AS Path prepending and Local Preference BGP settings should be used to ensure proper routing of traffic.
191198
192199
**Next steps**
193-
- Refer [SAP HANA (Large Instances) storage architecture](hana-storage-architecture.md)
200+
- Refer [SAP HANA (Large Instances) storage architecture](hana-storage-architecture.md)
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
author: ggailey777
3+
ms.service: app-service
4+
ms.topic: include
5+
ms.date: 10/13/2019
6+
ms.author: glenga
7+
---
8+
9+
> [!NOTE]
10+
> The default time zone used to run CRON expressions is Coordinated Universal Time (UTC). To have your CRON expression run based on another time zone, create an app setting for your function app named WEBSITE_TIME_ZONE. To learn more, see [NCRONTAB time zones](../articles/azure-functions/functions-bindings-timer.md#ncrontab-time-zones).

0 commit comments

Comments
 (0)