Skip to content

Commit a03e34a

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into filesADEnhance
2 parents 119f128 + 65c93f2 commit a03e34a

File tree

7 files changed

+66
-109
lines changed

7 files changed

+66
-109
lines changed

articles/active-directory/standards/memo-22-09-meet-identity-requirements.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ ms.collection: M365-identity-device-management
1717

1818
# Meeting identity requirements of Memorandum 22-09 with Azure Active Directory
1919

20+
Executive order [14028, Improving the Nation’s Cyber Security](https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity), directs federal agencies on advancing security measures that dramatically reduce the risk of successful cyber attacks against the federal government’s digital infrastructure. On January 26, 2022, the [Office of Management and Budget (OMB)](https://www.whitehouse.gov/omb/) released the Federal Zero Trust Strategy [Memorandum M-22-09](https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf) in support of EO 14028.
21+
2022
This series of articles offer guidance for employing Azure Active Directory (Azure AD) as a centralized identity management system for implementing Zero Trust principles as described by the US Federal Government’s Office of Management and Budget (OMB) [Memorandum M-22-09](https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf). Throughout this document we refer to it as "The memo."
2123

2224
The release of Memorandum 22-09 is designed to support Zero trust initiatives within federal agencies; it also provides regulatory guidance in supporting Federal Cybersecurity and Data Privacy Laws. The Memo cites the [Department of Defense (DoD) Zero Trust Reference Architecture](https://dodcio.defense.gov/Portals/0/Documents/Library/(U)ZT_RA_v1.1(U)_Mar21.pdf),

articles/communication-services/concepts/privacy.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,9 @@ The list of geographies you can choose from includes:
3232
- India
3333
- Japan
3434
- Korea
35+
- Norway
36+
- Switzerland
37+
- United Arab Emirates
3538
- United Kingdom
3639
- United States
3740

articles/healthcare-apis/azure-api-for-fhir/copy-to-synapse.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ginalee-dotcom
55
ms.service: healthcare-apis
66
ms.subservice: fhir
77
ms.topic: reference
8-
ms.date: 02/28/2022
8+
ms.date: 03/16/2022
99
ms.author: ginle
1010
---
1111

@@ -22,7 +22,7 @@ In this article, you'll learn three ways to copy data from Azure API for FHIR to
2222
> [!Note]
2323
> [FHIR to Synapse Sync Agent](https://github.com/microsoft/FHIR-Analytics-Pipelines/blob/main/FhirToDataLake/docs/Deployment.md) is an open source tool released under MIT license, and is not covered by the Microsoft SLA for Azure services.
2424
25-
The **FHIR to Synapse Sync Agent** is a Microsoft OSS project released under MIT License. It's an Azure function that extracts data from a FHIR server using FHIR Resource APIs, converts it to hierarchical Parquet files, and writes it to Azure Data Lake in near real time. This also contains a script to create external tables and views in [Synapse Serverless SQL pool](../../synapse-analytics/sql/on-demand-workspace-overview.md) pointing to the Parquet files.
25+
The **FHIR to Synapse Sync Agent** is a Microsoft OSS project released under MIT License. It's an Azure function that extracts data from a FHIR server using FHIR Resource APIs, converts it to hierarchical Parquet files, and writes it to Azure Data Lake in near real time. This also contains a script to create external tables and views in [Synapse Serverless SQL pool](https://docs.microsoft.com/azure/synapse-analytics/sql/on-demand-workspace-overview) pointing to the Parquet files.
2626

2727
This solution enables you to query against the entire FHIR data with tools such as Synapse Studio, SSMS, and Power BI. You can also access the Parquet files directly from a Synapse Spark pool. You should consider this solution if you want to access all of your FHIR data in near real time, and want to defer custom transformation to downstream systems.
2828

-52.7 KB
Loading

articles/healthcare-apis/azure-api-for-fhir/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
items:
2-
- name: Azure Healthcare APIs (preview) documentation
2+
- name: Azure Health Data Services documentation
33
href: ../index.yml
44
- name: Azure API for FHIR documentation
55
href: index.yml

0 commit comments

Comments
 (0)