You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/registration-config-change-token-lifetime-how-to.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ This article shows how to use Azure AD PowerShell to set an access token lifetim
26
26
To set an access token lifetime policy, download the [Azure AD PowerShell Module](https://www.powershellgallery.com/packages/AzureADPreview).
27
27
Run the **Connect-AzureAD -Confirm** command.
28
28
29
-
Here’s an example policy that requires users to authenticate more frequently in your web app. This policy sets the lifetime of the access to the service principal of your web app. Create the policy and assign it to your service principal. You also need to get the ObjectId of your service principal.
29
+
Here’s an example policy that requires users to authenticate less frequently in your web app. This policy sets the lifetime of the access to the service principal of your web app. Create the policy and assign it to your service principal. You also need to get the ObjectId of your service principal.
Copy file name to clipboardExpand all lines: articles/active-directory/governance/customize-workflow-email.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,6 +94,9 @@ Emails sent out using Lifecycle workflows can be customized to have your own com
94
94
- A verified domain. To add a custom domain, see: [Managing custom domain names in your Azure Active Directory](../enterprise-users/domains-manage.md)
95
95
- Custom Branding set within Azure AD if you want to have your custom branding used in emails. To set organizational branding within your Azure tenant, see: [Configure your company branding (preview)](../fundamentals/how-to-customize-branding.md).
96
96
97
+
> [!NOTE]
98
+
> The recommendation is to use a domain that has the appropriate DNS records to facilitate email validation, like SPF, DKIM, DMARC, and MX as this then complies with the [RFC compliance](https://www.ietf.org/rfc/rfc2142.txt) for sending and receiving email. Please see [Learn more about Exchange Online Email Routing](/exchange/mail-flow-best-practices/mail-flow-best-practices) for more information.
99
+
97
100
After these prerequisites are satisfied, you'd follow these steps:
98
101
99
102
1. On the Lifecycle workflows page, select **Workflow settings (Preview)**.
Copy file name to clipboardExpand all lines: articles/aks/configure-kubenet.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,16 +147,16 @@ az aks create \
147
147
--docker-bridge-address 172.17.0.1/16 \
148
148
--vnet-subnet-id $SUBNET_ID
149
149
```
150
-
* The *--service-cidr* is optional. This address is used to assign internal services in the AKS cluster an IP address. This IP address range should be an address space that isn't in use elsewhere in your network environment, including any on-premises network ranges if you connect, or plan to connect, your Azure virtual networks using Express Route or a Site-to-Site VPN connection.
150
+
* The *--service-cidr* is optional. This address is used to assign internal services in the AKS cluster an IP address. This IP address range should be an address space that isn't in use elsewhere in your network environment, including any on-premises network ranges if you connect, or plan to connect, your Azure virtual networks using Express Route or a Site-to-Site VPN connection. The default value is 10.0.0.0/16.
151
151
152
-
* The *--dns-service-ip* is optional. The address should be the *.10* address of your service IP address range.
152
+
* The *--dns-service-ip* is optional. The address should be the *.10* address of your service IP address range. The default value is 10.0.0.10.
153
153
154
-
* The *--pod-cidr* is optional. This address should be a large address space that isn't in use elsewhere in your network environment. This range includes any on-premises network ranges if you connect, or plan to connect, your Azure virtual networks using Express Route or a Site-to-Site VPN connection.
154
+
* The *--pod-cidr* is optional. This address should be a large address space that isn't in use elsewhere in your network environment. This range includes any on-premises network ranges if you connect, or plan to connect, your Azure virtual networks using Express Route or a Site-to-Site VPN connection. The default value is 10.244.0.0/16.
155
155
* This address range must be large enough to accommodate the number of nodes that you expect to scale up to. You can't change this address range once the cluster is deployed if you need more addresses for additional nodes.
156
156
* The pod IP address range is used to assign a */24* address space to each node in the cluster. In the following example, the *--pod-cidr* of *10.244.0.0/16* assigns the first node *10.244.0.0/24*, the second node *10.244.1.0/24*, and the third node *10.244.2.0/24*.
157
157
* As the cluster scales or upgrades, the Azure platform continues to assign a pod IP address range to each new node.
158
158
159
-
* The *--docker-bridge-address* is optional. The address lets the AKS nodes communicate with the underlying management platform. This IP address must not be within the virtual network IP address range of your cluster, and shouldn't overlap with other address ranges in use on your network.
159
+
* The *--docker-bridge-address* is optional. The address lets the AKS nodes communicate with the underlying management platform. This IP address must not be within the virtual network IP address range of your cluster, and shouldn't overlap with other address ranges in use on your network. The default value is 172.17.0.1/16.
160
160
161
161
> [!Note]
162
162
> If you wish to enable an AKS cluster to include a [Calico network policy][calico-network-policies] you can use the following command.
Copy file name to clipboardExpand all lines: articles/azure-maps/drawing-requirements.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -421,7 +421,7 @@ Below is the manifest file for the sample drawing package. Go to the [Sample dra
421
421
422
422
You can convert uploaded drawing packages into map data by using the Azure Maps [Conversion service]. This article describes the drawing package requirements for the Conversion API. To view a sample package, you can download the [sample drawing package v2].
423
423
424
-
For a guide on how to prepare your drawing package, see [Conversion Drawing Package Guide].
424
+
For a guide on how to prepare your drawing package, see [Drawing Package Guide].
425
425
426
426
## Changes and Revisions
427
427
@@ -667,7 +667,7 @@ The JSON in this example shows the manifest file for the sample drawing package.
667
667
668
668
## Next steps
669
669
670
-
For a guide on how to prepare your drawing package, see [Conversion Drawing Package Guide].
670
+
For a guide on how to prepare your drawing package, see the drawing package guide.
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-from-google-maps.md
+48-28Lines changed: 48 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.custom:
12
12
13
13
# Tutorial: Migrate from Google Maps to Azure Maps
14
14
15
-
This article provides insights on how to migrate web, mobile and server-based applications from Google Maps to the Microsoft Azure Maps platform. This tutorial includes comparative code samples, migration suggestions, and best practices for migrating to Azure Maps. In this tutorial, you'll learn:
15
+
This article provides insights on how to migrate web, mobile and server-based applications from Google Maps to the Microsoft Azure Maps platform. This tutorial includes comparative code samples, migration suggestions, and best practices for migrating to Azure Maps. This tutorial demonstrates:
16
16
17
17
> [!div class="checklist"]
18
18
> * High-level comparison for equivalent Google Maps features available in Azure Maps.
@@ -28,15 +28,15 @@ If you don't have an Azure subscription, create a [free account] before you begi
28
28
* A [subscription key]
29
29
30
30
> [!NOTE]
31
-
> For more information on authentication in Azure Maps, see [manage authentication in Azure Maps].
31
+
> For more information on authentication in Azure Maps, see [Manage authentication in Azure Maps].
32
32
33
33
## Azure Maps platform overview
34
34
35
35
Azure Maps provides developers from all industries powerful geospatial capabilities. The capabilities are packed with regularly updated map data to provide geographic context for web, and mobile applications. Azure Maps has an Azure One API compliant set of REST APIs. The REST APIs offer Maps Rendering, Search, Routing, Traffic, Time Zones, Geolocation, Geofencing, Map Data, Weather, and Spatial Operations. Operations are accompanied by both Web and Android SDKs to make development easy, flexible, and portable across multiple platforms.
36
36
37
37
## High-level platform comparison
38
38
39
-
The table provides a high-level list of Azure Maps features, which correspond to Google Maps features. This list doesn't show all Azure Maps features. Additional Azure Maps features include: accessibility, geofencing, isochrones, spatial operations, direct map tile access, batch services, and data coverage comparisons (that is, imagery coverage).
39
+
The table provides a high-level list of Azure Maps features, which correspond to Google Maps features. This list doesn't show all Azure Maps features. Other Azure Maps features include: accessibility, geofencing, isochrones, spatial operations, direct map tile access, batch services, and data coverage comparisons (that is, imagery coverage).
@@ -62,7 +62,7 @@ The table provides a high-level list of Azure Maps features, which correspond to
62
62
| Maps Embedded API | N/A |
63
63
| Map URLs | N/A |
64
64
65
-
<sup>1</sup> Azure Maps [Elevation services](/rest/api/maps/elevation) have been [deprecated](https://azure.microsoft.com/updates/azure-maps-elevation-apis-and-render-v2-dem-tiles-will-be-retired-on-5-may-2023). For more information how to include this functionality in your Azure Maps, see [Create elevation data & services](elevation-data-services.md).
65
+
<sup>1</sup> Azure Maps [Elevation services] have been [deprecated]. For more information how to include this functionality in your Azure Maps, see [Create elevation data & services].
66
66
67
67
Google Maps provides basic key-based authentication. Azure Maps provides both basic key-based authentication and Azure Active Directory authentication. Azure Active Directory authentication provides more security features, compared to the basic key-based authentication.
68
68
@@ -72,23 +72,22 @@ When migrating to Azure Maps from Google Maps, consider the following points abo
72
72
73
73
* Azure Maps charges for the usage of interactive maps, which is based on the number of loaded map tiles. On the other hand, Google Maps charges for loading the map control. In the interactive Azure Maps SDKs, map tiles are automatically cached to reduce the development cost. One Azure Maps transaction is generated for every 15 map tiles that are loaded. The interactive Azure Maps SDKs uses 512-pixel tiles, and on average, it generates one or less transactions per page view.
74
74
* Often, it's more cost effective to replace static map images from Google Maps web services with the Azure Maps Web SDK. The Azure Maps Web SDK uses map tiles. Unless the user pans and zooms the map, the service often generates only a fraction of a transaction per map load. The Azure Maps web SDK has options for disabling panning and zooming, if desired. Additionally, the Azure Maps web SDK provides a lot more visualization options than the static map web service.
75
-
* Azure Maps allows data from its platform to be stored in Azure. Also, data can be cached elsewhere for up to six months as per the [terms of use](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=46).
75
+
* Azure Maps allows data from its platform to be stored in Azure. Also, data can be cached elsewhere for up to six months as per the [terms of use].
*[Azure Maps term of use](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=46)
82
-
(included in the Microsoft Online Services Terms)
83
-
*[Choose the right pricing tier in Azure Maps](./choose-pricing-tier.md)
79
+
*[Azure Maps pricing page]
80
+
*[Azure pricing calculator]
81
+
*[Choose the right pricing tier in Azure Maps]
82
+
*[Azure Maps term of use] - included in the Microsoft Online Services Terms.
84
83
85
84
## Suggested migration plan
86
85
87
-
The following is a high-level migration plan.
86
+
A high-level migration plan includes.
88
87
89
88
1. Take inventory of the Google Maps SDKs and services that your application uses. Verify that Azure Maps provides alternative SDKs and services.
90
-
2. If you don't already have one, create an Azure subscription at [https://azure.com](https://azure.com).
91
-
3. Create an Azure Maps account ([documentation](./how-to-manage-account-keys.md)) and authentication key or Azure Active Directory ([documentation](./how-to-manage-authentication.md)).
89
+
2. If you don't already have one, create an [Azure subscription].
90
+
3. Create an [Azure Maps account] and [subscription key] or [Azure Active Directory authentication].
92
91
4. Migrate your application code.
93
92
5. Test your migrated application.
94
93
6. Deploy your migrated application to production.
@@ -97,28 +96,26 @@ The following is a high-level migration plan.
97
96
98
97
To create an Azure Maps account and get access to the Azure Maps platform, follow these steps:
99
98
100
-
1. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/) before you begin.
101
-
2. Sign in to the [Azure portal](https://portal.azure.com/).
102
-
3. Create an [Azure Maps account](./how-to-manage-account-keys.md).
103
-
4.[Get your Azure Maps subscription key](./how-to-manage-authentication.md#view-authentication-details) or setup Azure Active Directory authentication for enhanced security.
99
+
1. If you don't have an Azure subscription, create a [free account] before you begin.
100
+
2. Sign in to the [Azure portal].
101
+
3. Create an [Azure Maps account].
102
+
4. Get your Azure Maps [subscription key] or [Azure Active Directory authentication] for enhanced security.
104
103
105
104
## Azure Maps technical resources
106
105
107
106
Here's a list of useful technical resources for Azure Maps.
Developers can seek migration support through the [forums](/answers/topics/azure-maps.html) or through one of the many Azure support options: [https://azure.microsoft.com/support/options](https://azure.microsoft.com/support/options)
118
+
Developers can seek migration support through the [Azure Maps developer forums] or through one of the many [Azure support options].
122
119
123
120
## Clean up resources
124
121
@@ -134,4 +131,27 @@ Learn the details of how to migrate your Google Maps application with these arti
0 commit comments