Skip to content

Commit

Permalink
Why do links need to be so expletive difficult????
Browse files Browse the repository at this point in the history
  • Loading branch information
steelanddata committed Feb 18, 2016
1 parent 32ff0da commit 5fa4654
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion articles/data-catalog/data-catalog-whats-new.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ As of the week of February 19, 2016, the following capabilities have been added

- A newly redesigned data source selection experience in the **Azure Data Catalog** data source registration tool. The data source registration tool has been updated to make it easier for users to locate and select from the data sources supported by **Azure Data Catalog**.
- Support for ten additional languages in the **Azure Data Catalog** portal and the data source registration tool. In addition to English, the **Azure Data Catalog** experience is now available in German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Russian, Simplified Chinese, and Traditional Chinese. The **Azure Data Catalog** user experience will be localized based on the language preferences set in Windows or in the user’s web browser.
- Support for geo-replication of **Azure Data Catalog** data for business continuity and disaster recovery. All **Azure Data Catalog** contents, including data source metadata and crowdsourced annotations, are now replicated between two Azure regions at no additional cost to customers. The Azure regions are pre-paired, at least 500 miles apart, and follow the mapping as described in [Business continuity and disaster recovery (BCDR): Azure Paired Regions](best-practices-availability-paired-regions/).
- Support for geo-replication of **Azure Data Catalog** data for business continuity and disaster recovery. All **Azure Data Catalog** contents, including data source metadata and crowdsourced annotations, are now replicated between two Azure regions at no additional cost to customers. The Azure regions are pre-paired, at least 500 miles apart, and follow the mapping as described in [Business continuity and disaster recovery (BCDR): Azure Paired Regions](best-practices-availability-paired-regions.md).


## What's new for the week of February 5, 2016 release
Expand Down

0 comments on commit 5fa4654

Please sign in to comment.