Skip to content

Commit 07886ce

Browse files
committed
Removed 'preview' tag related to CORS.
1 parent 1f35d80 commit 07886ce

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

articles/azure-maps/azure-maps-authentication.md

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -286,25 +286,19 @@ After the application receives a SAS token, the Azure Maps SDK and/or applicatio
286286
287287
## Cross origin resource sharing (CORS)
288288

289-
[!INCLUDE [preview features callout](./includes/preview-callout.md)]
289+
[CORS] is an HTTP protocol that enables a web application running under one domain to access resources in another domain. Web browsers implement a security restriction known as [same-origin policy] that prevents a web page from calling APIs in a different domain; CORS provides a secure way to allow one domain (the origin domain) to call APIs in another domain. Using the Azure Maps account resource, you can configure which origins are allowed to access the Azure Maps REST API from your applications.
290290

291-
Cross Origin Resource Sharing (CORS) is in preview.
291+
> [!IMPORTANT]
292+
> CORS is not an authorization mechanism. Any request made to a map account using REST API, when CORS is enabled, also needs a valid map account authentication scheme such as Shared Key, Azure AD, or SAS token.
293+
>
294+
> CORS is supported for all map account pricing tiers, data-plane endpoints, and locations.
292295
293296
### Prerequisites
294297

295298
To prevent malicious code execution on the client, modern browsers block requests from web applications to resources running in a separate domain.
296299

297300
- If you're unfamiliar with CORS, see [Cross-origin resource sharing (CORS)], it lets an `Access-Control-Allow-Origin` header declare which origins are allowed to call endpoints of an Azure Maps account. CORS protocol isn't specific to Azure Maps.
298301

299-
### Account CORS
300-
301-
[CORS] is an HTTP protocol that enables a web application running under one domain to access resources in another domain. Web browsers implement a security restriction known as [same-origin policy] that prevents a web page from calling APIs in a different domain; CORS provides a secure way to allow one domain (the origin domain) to call APIs in another domain. Using the Azure Maps account resource, you can configure which origins are allowed to access the Azure Maps REST API from your applications.
302-
303-
> [!IMPORTANT]
304-
> CORS is not an authorization mechanism. Any request made to a map account using REST API, when CORS is enabled, also needs a valid map account authentication scheme such as Shared Key, Azure AD, or SAS token.
305-
>
306-
> CORS is supported for all map account pricing tiers, data-plane endpoints, and locations.
307-
308302
### CORS requests
309303

310304
A CORS request from an origin domain may consist of two separate requests:

0 commit comments

Comments
 (0)