Skip to content

Commit 6745599

Browse files
authored
Merge branch 'MicrosoftDocs:main' into patch-3
2 parents 0834ad2 + 0bac163 commit 6745599

File tree

9 files changed

+131
-37
lines changed

9 files changed

+131
-37
lines changed

articles/active-directory/develop/configure-token-lifetimes.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,29 +9,30 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 04/08/2021
12+
ms.date: 10/17/2022
1313
ms.author: ryanwi
14-
ms.custom: aaddev, contperf-fy21q1
14+
ms.custom: identityplatformtop40, contperf-fy21q2, engagement-fy23
1515
ms.reviewer: ludwignick, jlu, annaba
1616
---
1717
# Configure token lifetime policies (preview)
18-
You can specify the lifetime of an access, SAML, or ID token issued by Microsoft identity platform. You can set token lifetimes for all apps in your organization, for a multi-tenant (multi-organization) application, or for a specific service principal in your organization. For more info, read [configurable token lifetimes](active-directory-configurable-token-lifetimes.md).
1918

20-
In this section, we walk through a common policy scenario that can help you impose new rules for token lifetime. In the example, you learn how to create a policy that requires users to authenticate more frequently in your web app.
19+
In the following steps, you'll implement a common policy scenario that imposes new rules for token lifetime. It's possible to specify the lifetime of an access, SAML, or ID token issued by the Microsoft identity platform. This can be set for all apps in your organization or for a specific service principal. They can also be set for multi-organizations (multi-tenant application).
20+
21+
For more information, see [configurable token lifetimes](active-directory-configurable-token-lifetimes.md).
2122

2223
## Get started
2324

2425
To get started, download the latest [Azure AD PowerShell Module Public Preview release](https://www.powershellgallery.com/packages/AzureADPreview).
2526

26-
Next, run the `Connect` command to sign in to your Azure AD admin account. Run this command each time you start a new session.
27+
Next, run the `Connect-AzureAD` command to sign in to your Azure Active Directory (Azure AD) admin account. Run this command each time you start a new session.
2728

2829
```powershell
2930
Connect-AzureAD -Confirm
3031
```
3132

3233
## Create a policy for web sign-in
3334

34-
In this example, you create a policy that requires users to authenticate more frequently in your web app. This policy sets the lifetime of the access/ID tokens to the service principal of your web app.
35+
In the following steps, you'll create a policy that requires users to authenticate more frequently in your web app. This policy sets the lifetime of the access/ID tokens to the service principal of your web app.
3536

3637
1. Create a token lifetime policy.
3738

@@ -73,7 +74,7 @@ To see all policies that have been created in your organization, run the [Get-Az
7374
Get-AzureADPolicy -All $true
7475
```
7576

76-
To see which apps and service principals are linked to a specific policy you identified run the following [Get-AzureADPolicyAppliedObject](/powershell/module/azuread/get-azureadpolicyappliedobject?view=azureadps-2.0-preview&preserve-view=true) cmdlet by replacing **1a37dad8-5da7-4cc8-87c7-efbc0326cf20** with any of your policy IDs. Then you can decide whether to configure Conditional Access sign-in frequency or remain with the Azure AD defaults.
77+
To see which apps and service principals are linked to a specific policy that you identified, run the following [`Get-AzureADPolicyAppliedObject`](/powershell/module/azuread/get-azureadpolicyappliedobject?view=azureadps-2.0-preview&preserve-view=true) cmdlet by replacing `1a37dad8-5da7-4cc8-87c7-efbc0326cf20` with any of your policy IDs. Then you can decide whether to configure Conditional Access sign-in frequency or remain with the Azure AD defaults.
7778

7879
```powershell
7980
Get-AzureADPolicyAppliedObject -id 1a37dad8-5da7-4cc8-87c7-efbc0326cf20
@@ -82,7 +83,7 @@ Get-AzureADPolicyAppliedObject -id 1a37dad8-5da7-4cc8-87c7-efbc0326cf20
8283
If your tenant has policies which define custom values for the refresh and session token configuration properties, Microsoft recommends you update those policies to values that reflect the defaults described above. If no changes are made, Azure AD will automatically honor the default values.
8384

8485
### Troubleshooting
85-
Some users have reported a `Get-AzureADPolicy : The term 'Get-AzureADPolicy' is not recognized` error after running the `Get-AzureADPolicy` cmdlet. As a workaround, run the following to uninstall/re-install the AzureAD module and then install the AzureADPreview module:
86+
Some users have reported a `Get-AzureADPolicy : The term 'Get-AzureADPolicy' is not recognized` error after running the `Get-AzureADPolicy` cmdlet. As a workaround, run the following to uninstall/re-install the AzureAD module, and then install the AzureADPreview module:
8687

8788
```powershell
8889
# Uninstall the AzureAD Module

articles/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ This QuickStart shows you how to connect your SCVMM management server to Azure A
1616

1717
## Prerequisites
1818

19+
>[!Note]
20+
>If VMM server is running on Windows Server 2016 machine, ensure that [Open SSH package](https://github.com/PowerShell/Win32-OpenSSH/releases) is installed.
21+
1922
| **Requirement** | **Details** |
2023
| --- | --- |
2124
| **Azure** | An Azure subscription <br/><br/> A resource group in the above subscription where you have the *Owner/Contributor* role. |

articles/data-factory/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -288,14 +288,14 @@ items:
288288
- name: Supported functions
289289
href: wrangling-functions.md
290290
displayName: power
291+
- name: Change Data Capture
292+
href: concepts-change-data-capture.md
291293
- name: Roles and permissions
292294
href: concepts-roles-permissions.md
293295
- name: Naming rules
294296
href: naming-rules.md
295297
- name: Data redundancy
296298
href: concepts-data-redundancy.md
297-
- name: Change Data Capture
298-
href: concepts-change-data-capture.md
299299
- name: SAP knowledge center
300300
items:
301301
- name: Overview

articles/data-factory/concepts-change-data-capture.md

Lines changed: 57 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: data-factory
99
ms.subservice: data-movement
1010
ms.custom: synapse
1111
ms.topic: conceptual
12-
ms.date: 10/14/2022
12+
ms.date: 10/18/2022
1313
---
1414

1515
# Change data capture in Azure Data Factory and Azure Synapse Analytics
@@ -22,30 +22,68 @@ To learn more, see [Azure Data Factory overview](introduction.md) or [Azure Syna
2222

2323
## Overview
2424

25-
When you perform data integration and ETL processes in the cloud, your jobs can perform much better and be more effective when you only read the source data that has changed since the last time the pipeline ran, rather than always querying an entire dataset on each run. Executing pipelines that only read the latest changed data is available in many of ADF's source connectors by simply enabling a checkbox property inside the source transformation. Support for full-fidelity CDC, which includes row markers for inserts, upserts, deletes, and updates, as well as rules for resetting the ADF-managed checkpoint are available in several ADF connectors. To easily capture changes and deltas, ADF supports patterns and templates for managing incremental pipelines with user-controlled checkpoints as well, which you'll find in the table below.
25+
When you perform data integration and ETL processes in the cloud, your jobs can perform much better and be more effective when you only read the source data that has changed since the last time the pipeline ran, rather than always querying an entire dataset on each run. ADF provides multiple different ways for you to easily get delta data only from the last run.
2626

27-
## CDC Connector support
27+
### Native change data capture in mapping data flow
2828

29-
| Connector | Full CDC | Incremental CDC | Incremental pipeline pattern |
30-
| :-------------------- | :--------------------------- | :--------------------------------- | :--------------------------- |
31-
| [ADLS Gen1](load-azure-data-lake-store.md) | &nbsp; || &nbsp; |
32-
| [ADLS Gen2](load-azure-data-lake-storage-gen2.md) | &nbsp; || &nbsp; |
33-
| [Azure Blob Storage](connector-azure-blob-storage.md) | &nbsp; || &nbsp; |
34-
| [Azure Cosmos DB (SQL API)](connector-azure-cosmos-db.md) ||| &nbsp; |
35-
| [Azure Database for MySQL](connector-azure-database-for-mysql.md) | &nbsp; || &nbsp; |
36-
| [Azure Database for PostgreSQL](connector-azure-database-for-postgresql.md) | &nbsp; || &nbsp; |
37-
| [Azure SQL Database](connector-azure-sql-database.md) ||| [](tutorial-incremental-copy-portal.md) |
38-
| [Azure SQL Managed Instance](connector-azure-sql-managed-instance.md) ||| [](tutorial-incremental-copy-change-data-capture-feature-portal.md) |
39-
| [Azure SQL Server](connector-sql-server.md) ||| [](tutorial-incremental-copy-multiple-tables-portal.md) |
40-
| [Common data model](format-common-data-model.md) | &nbsp; || &nbsp; |
41-
| [SAP CDC](connector-sap-change-data-capture.md) ||||
29+
The changed data including inserted, updated and deleted rows can be automatically detected and extracted by ADF mapping data flow from the source databases. No timestamp or ID columns are required to identify the changes since it uses the native change data capture technology in the databases. By simply chaining a source transform and a sink transform reference to a database dataset in a mapping data flow, you will see the changes happened on the source database to be automatically applied to the target database, so that you can easily synchronize data between two tables. You can also add any transformations in between for any business logic to process the delta data.
4230

31+
**Supported connectors**
32+
- [SAP CDC](connector-sap-change-data-capture.md)
33+
- [Azure SQL Database](connector-azure-sql-database.md)
34+
- [Azure SQL Server](connector-sql-server.md)
35+
- [Azure SQL Managed Instance](connector-azure-sql-managed-instance.md)
36+
- [Azure Cosmos DB (SQL API)](connector-azure-cosmos-db.md)
4337

44-
ADF makes it super-simple to enable and use CDC. Many of the connectors listed above will enable a checkbox similar to the one shown below from the data flow source transformation.
38+
### Auto incremental extraction in mapping data flow
4539

46-
:::image type="content" source="media/data-flow/cdc.png" alt-text="Change data capture":::
40+
The newly updated rows or updated files can be automatically detected and extracted by ADF mapping data flow from the source stores. When you want to get delta data from the databases, the incremental column is required to identify the changes. When you want to load new files or updated files only from a storage store, ADF mapping data flow just works through files’ last modify time.
41+
42+
**Supported connectors**
43+
- [Azure Blob Storage](connector-azure-blob-storage.md)
44+
- [ADLS Gen2](load-azure-data-lake-storage-gen2.md)
45+
- [ADLS Gen1](load-azure-data-lake-store.md)
46+
- [Azure SQL Database](connector-azure-sql-database.md)
47+
- [Azure SQL Server](connector-sql-server.md)
48+
- [Azure SQL Managed Instance](connector-azure-sql-managed-instance.md)
49+
- [Azure Database for MySQL](connector-azure-database-for-mysql.md)
50+
- [Azure Database for PostgreSQL](connector-azure-database-for-postgresql.md)
51+
- [Common data model](format-common-data-model.md)
52+
53+
### Customer managed delta data extraction in pipeline
54+
55+
You can always build your own delta data extraction pipeline for all ADF supported data stores including using lookup activity to get the watermark value stored in an external control table, copy activity or mapping data flow activity to query the delta data against timestamp or ID column, and SP activity to write the new watermark value back to your external control table for the next run. When you want to load new files only from a storage store, you can either delete files every time after they have been moved to the destination successfully, or leverage the time partitioned folder or file names or last modified time to identify the new files.
56+
57+
58+
## Best Practices
59+
60+
**Change data capture from databases:**
61+
62+
- Native change data capture is always recommended as the simplest way for you to get change data. It also brings much less burden on your source database when ADF extracts the change data for further processing.
63+
- If your database stores are not part of the ADF connector list with native change data capture support, we recommend you to check the auto incremental extraction option where you only need to input incremental column to capture the changes. ADF will take care of the rest including creating a dynamic query for delta loading and managing the checkpoint for each activity run.
64+
- Customer managed delta data extraction in pipeline covers all the ADF supported databases and give you the flexibility to control everything by yourself.
65+
66+
**Change files capture from file based storages:**
67+
68+
- When you want to load data from Azure Blob Storage, Azure Data Lake Storage Gen2 or Azure Data Lake Storage Gen1, mapping data flow provides you the opportunity to get new or updated files only by simple one click. It is the simplest and recommended way for you to achieve delta load from these file based storages in mapping data flow.
69+
- You can get more [best practices](https://techcommunity.microsoft.com/t5/azure-data-factory-blog/best-practices-of-how-to-use-adf-copy-activity-to-copy-new-files/ba-p/1532484).
70+
71+
72+
## Checkpoint
73+
74+
When you enable native change data capture or auto incremental extraction options in ADF mapping data flow, ADF helps you to manage the checkpoint to make sure each activity run will automatically only read the source data that has changed since the last time the pipeline run. By default, the checkpoint is coupled with your pipeline and activity name. If you change your pipeline name or activity name, the checkpoint will be reset, which leads you to start from beginning or get changes from now in the next run. If you do want to change the pipeline name or activity name but still keep the checkpoint to get changed data from the last run automatically, please use your own [Checkpoint key](control-flow-execute-data-flow-activity.md#checkpoint-key) in data flow activity to achieve that.
75+
76+
When you debug the pipeline, this feature works the same. The checkpoint will be reset when you refresh your browser during the debug run. After you are satisfied with the pipeline result from debug run, you can go ahead to publish and trigger the pipeline. At the moment when you first time trigger your published pipeline, it automatically restarts from the beginning or gets changes from now on.
77+
78+
In the monitoring section, you always have the chance to rerun a pipeline. When you are doing so, the changed data is always captured from the previous checkpoint of your selected pipeline run.
79+
80+
## Tutorials
81+
82+
The followings are the tutorials to start the change data capture in Azure Data Factory and Azure Synapse Analytics.
83+
84+
- [SAP CDC tutorial in ADF](sap-change-data-capture-introduction-architecture.md#sap-cdc-capabilities)
85+
- [Incrementally copy data from a source data store to a destination data store tutorials](tutorial-incremental-copy-overview.md)
4786

48-
The "Full CDC" and "Incremental CDC" features are available in both ADF and Synapse data flows and pipelines. In each of those options, ADF manages the checkpoint automatically for you. You can turn on the change data capture feature in the data flow source and you can also reset the checkpoint in the data flow activity. To reset the checkpoint for your CDC pipeline, go into the data flow activity in your pipeline and override the checkpoint key. Connectors in ADF that support "full CDC" also provide automatic tagging of rows as update, insert, delete.
4987

5088
## Next steps
5189

articles/defender-for-cloud/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -517,7 +517,9 @@
517517
- name: Defender for Servers integration with Microsoft Defender for Endpoint
518518
href: episode-sixteen.md
519519
- name: Defender for Servers integration with Microsoft Entra
520-
href: episode-seventeen.md
520+
href: episode-seventeen.md
521+
- name: Defender for Azure Cosmos DB
522+
href: episode-eighteen.md
521523
- name: Manage user data
522524
href: privacy.md
523525
- name: Microsoft Defender for IoT documentation

articles/defender-for-cloud/concept-cloud-security-posture-management.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Defender for Cloud continually assesses your resources, subscriptions, and organ
2121

2222
## Defender CSPM plan options
2323

24-
The Defender CSPM plan comes with two options, foundational CSPM capabilities and Defender Cloud Security Posture Management (CSPM). When you deploy Defender for Cloud to your subscription and resources, you'll automatically gain the basic coverages offered by the CSPM plan. To gain access to the other capabilities provided by Defender CSPM, you'll need to [enable the Defender Cloud Security Posture Management (CSPM) plan](enable-enhanced-security.md) to your subscription and resources.
24+
The Defender CSPM plan comes with two options, foundational CSPM capabilities and Defender Cloud Security Posture Management (CSPM). When you deploy Defender for Cloud to your subscription and resources, you'll automatically gain the basic coverage offered by the CSPM plan. To gain access to the other capabilities provided by Defender CSPM, you'll need to [enable the Defender Cloud Security Posture Management (CSPM) plan](enable-enhanced-security.md) on your subscription and resources.
2525

2626
The following table summarizes what's included in each plan and their cloud availability.
2727

@@ -60,11 +60,14 @@ Learn more about [Cloud Security Explorer](concept-attack-path.md#what-is-cloud-
6060

6161
## Attack Path Analysis
6262

63-
Attack Path Analysis is a graph-based algorithm that scans the Cloud Security Graph. The scans expose exploitable paths that attackers may use to breach your environment to reach your high-impact assets. Attack Path Analysis exposes those attack paths and suggests recommendations as to how best remediate the issues that will break the attack path and prevent successful breach.
63+
Attack Path Analysis is a graph-based algorithm that scans the Cloud Security Graph. The scans:
6464

65-
By taking your environment's contextual information into account such as, internet exposure, permissions, lateral movement, and more. Attack Path Analysis identifies issues that may lead to a breach on your environment, and helps you to remediate the highest risk ones first.
65+
- expose exploitable paths that attackers may use to breach your environment and reach your high-impact assets
66+
- provide recommendations for ways to prevent successful breaches
6667

67-
Learn more about [Attack Path Analysis](concept-attack-path.md#what-is-attack-path-analysis)
68+
By taking your environment's contextual information into account such as, internet exposure, permissions, lateral movement, and more, this analysis identifies issues that may lead to a breach on your environment, and helps you to remediate the highest risk ones first.
69+
70+
Learn more about [Attack Path Analysis](concept-attack-path.md#what-is-attack-path-analysis).
6871

6972
## Agentless scanning for machines
7073

0 commit comments

Comments
 (0)