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/hybrid/connect/tshoot-connect-password-hash-synchronization.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,10 +174,12 @@ password hash synchronization for this on-premises Active Directory account fail
174
174
175
175
#### User has a temporary password
176
176
177
-
Currently, Azure AD Connect does not support synchronizing temporary passwords with Azure AD. A password is considered to be temporary if the **Change password at next logon** option is set on the on-premises Active Directory user. The following error is returned:
177
+
Older versions of Azure AD Connect did not support synchronizing temporary passwords with Azure AD. A password is considered to be temporary if the **Change password at next logon** option is set on the on-premises Active Directory user. The following error is returned with these older versions:
178
178
179
179

180
180
181
+
To enable synchonization of temporary passwords you must have Azure AD Connect version 2.0.3.0 or higher installed and the feature [ForcePasswordChangeOnLogon](../connect/how-to-connect-password-hash-synchronization.md#synchronizing-temporary-passwords-and-force-password-change-on-next-logon) must be enabled.
182
+
181
183
#### Results of last attempt to synchronize password aren't available
182
184
183
185
By default, Azure AD Connect stores the results of password hash synchronization attempts for seven days. If there are no results available for the selected Active Directory object, the following warning is returned:
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-from-bing-maps-web-services.md
+53-69Lines changed: 53 additions & 69 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,7 +120,7 @@ Azure Maps also supports:
120
120
Azure Maps also supports:
121
121
122
122
*`typeahead` - Specifies if the query is interpreted as a partial input and the search enters predictive mode (autosuggest/autocomplete).
123
-
*`countrySet` – A comma-separated list of ISO2 countries codes in which to limit the search to.
123
+
*`countrySet` – A comma-separated list of ISO2 country codes in which to limit the search to.
124
124
*`lat`/`lon`, `topLeft`/`btmRight`, `radius` – Specify user location and area to make the results more locally relevant.
125
125
*`ofs` - Page through the results in combination with `maxResults` parameter.
126
126
@@ -219,7 +219,7 @@ The following table cross-references the Bing Maps API parameters with the compa
219
219
|`culture` (`c`) |`language` – For more information, see [Localization support in Azure Maps]. |
220
220
|`userRegion` (`ur`) |`view` – For more information, see [Azure Maps supported views]. |
221
221
222
-
The Azure Maps routing API also supports truck routing within the same API. The following table cross-references the additional Bing Maps truck routing parameters with the comparable API parameters in Azure Maps.
222
+
The Azure Maps routing API also supports truck routing within the same API. The following table cross-references the other Bing Maps truck routing parameters with the comparable API parameters in Azure Maps.
223
223
224
224
| Bing Maps API parameter | Comparable Azure Maps API parameter |
@@ -285,7 +285,7 @@ The following table cross-references the Bing Maps API parameters with the compa
285
285
|`culture` (`c`) |`language` – For more information, see [Localization support in Azure Maps]. |
286
286
|`userRegion` (`ur`) |`view` – For more information, see [Azure Maps supported views]. |
287
287
288
-
The Azure Maps routing API also supports truck routing parameter within the same API to ensure logical paths are calculated. The following table cross-references the additional Bing Maps truck routing parameters with the comparable API parameters in Azure Maps.
288
+
The Azure Maps routing API also supports truck routing parameter within the same API to ensure logical paths are calculated. The following table cross-references the other Bing Maps truck routing parameters with the comparable API parameters in Azure Maps.
289
289
290
290
| Bing Maps API parameter | Comparable Azure Maps API parameter |
@@ -313,7 +313,7 @@ The Azure Maps route directions API doesn't currently return speed limit data, h
313
313
314
314
The Azure Maps Web SDK uses vector tiles to render the maps. These vector tiles contain the raw road geometry information and can be used to calculate the nearest road to a coordinate for simple snapping of individual coordinates. This is useful when you want the coordinates to visually appear over roads and you're already using the Azure Maps Web SDK to visualize the data.
315
315
316
-
This approach however will only snap to the road segments that are loaded within the map view. When zoomed out at country/region level there may be no road data, so snapping can’t be done, however at that zoom level a single pixel can represent the area of several city blocks so snapping isn’t needed. To address this, the snapping logic can be applied every time the map has finished moving. To see a fully functional example of this snapping logic, see the [Basic snap to road logic] sample in the Azure Maps samples.
316
+
This approach however only snaps to the road segments that are loaded within the map view. When zoomed out at country/region level there may be no road data, so snapping can’t be done, however at that zoom level a single pixel can represent the area of several city blocks so snapping isn’t needed. To address this, the snapping logic can be applied every time the map has finished moving. To see a fully functional example of this snapping logic, see the [Basic snap to road logic] sample in the Azure Maps samples.
317
317
318
318
**Using the Azure Maps vector tiles directly to snap coordinates**
319
319
@@ -384,7 +384,7 @@ In Azure Maps, pushpins can also be added to a static map image by specifying th
Additional styles can be used by adding more `pins` parameters to the URL with a different style and set of locations.
387
+
More styles can be used by adding more `pins` parameters to the URL with a different style and set of locations.
388
388
389
389
Regarding pin locations, Azure Maps requires the coordinates to be in `longitude latitude` format whereas Bing Maps uses `latitude,longitude` format. Also note that **there is a space, not a comma** separating longitude and latitude in Azure Maps.
390
390
@@ -428,7 +428,7 @@ In Bing Maps, lines, and polygons can be added to a static map image by using th
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-from-bing-maps.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ The following table provides a high-level list of Bing Maps features and the rel
67
67
| Traffic Incidents | ✓ |
68
68
| Configuration driven maps | N/A |
69
69
70
-
<sup>1</sup> While there is no direct replacement for the Bing Maps *Snap to road* service, this functionality can be implemented using the Azure Maps [Route - Get Route Directions] REST API. For a complete code sample demonstrating the snap to road functionality, see the [Basic snap to road logic] sample that demonstrates how to snap individual points to the rendered roads on the map. Also see the [Snap points to logical route path] sample that shows how to snap points to the road network to form a logical path.
70
+
<sup>1</sup> While there's no direct replacement for the Bing Maps *Snap to road* service, this functionality can be implemented using the Azure Maps [Route - Get Route Directions] REST API. For a complete code sample demonstrating the snap to road functionality, see the [Basic snap to road logic] sample that demonstrates how to snap individual points to the rendered roads on the map. Also see the [Snap points to logical route path] sample that shows how to snap points to the road network to form a logical path.
71
71
72
72
Bing Maps provides basic key-based authentication. Azure Maps provides both basic key-based authentication and highly secure, Azure Active Directory authentication.
73
73
@@ -153,30 +153,31 @@ There are no resources that require cleanup.
153
153
Learn the details of how to migrate your Bing Maps application with these articles:
154
154
155
155
> [!div class="nextstepaction"]
156
-
> [Migrate a web app](migrate-from-bing-maps-web-app.md)
156
+
> [Migrate a web app]
157
157
158
+
[Azure Active Directory authentication]: azure-maps-authentication.md#azure-ad-authentication
0 commit comments