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/app-service/deploy-staging-slots.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Set up Staging Environments in Azure App Service
2
+
title: Set Up Staging Environments
3
3
description: Learn how to deploy apps to a nonproduction slot and automatically swap into production. Increase the reliability and eliminate app downtime from deployments.
Copy file name to clipboardExpand all lines: articles/app-service/overview-authentication-authorization.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Authentication and Authorization in Azure App Service and Azure Functions
2
+
title: Authentication and Authorization
3
3
description: Learn about the built-in authentication and authorization support in Azure App Service and Azure Functions, and how it can help secure your app against unauthorized access.
Copy file name to clipboardExpand all lines: articles/app-service/overview-managed-identity.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Use managed identities for App Service and Azure Functions
2
+
title: Managed Identities
3
3
description: Learn how managed identities work in Azure App Service and Azure Functions, along with how to configure a managed identity and generate a token for a back-end resource.
Copy file name to clipboardExpand all lines: articles/app-service/troubleshoot-diagnostic-logs.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Enable Diagnostic Logging for Apps in Azure App Service
2
+
title: Enable Diagnostic Logging
3
3
description: Learn how to enable diagnostic logging and add instrumentation to your application, along with how to access the information logged by Azure.
Copy file name to clipboardExpand all lines: articles/automation/delete-account.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article tells how to delete and your Automation account across
4
4
services: automation
5
5
ms.service: azure-automation
6
6
ms.subservice: process-automation
7
-
ms.date: 12/28/2024
7
+
ms.date: 03/20/2025
8
8
ms.topic: how-to
9
9
---
10
10
@@ -93,6 +93,9 @@ While it attempts to unlink the Automation account, you can track the progress u
93
93
94
94
After the Automation account is successfully unlinked from the workspace, perform the steps in the [standalone Automation account](#delete-a-standalone-automation-account) section to delete the account.
95
95
96
+
> [!NOTE]
97
+
> A previously soft-deleted Log Analytics workspace can't be unlinked from the Automation account successfully. In this scenario, first recover and permanently delete it to forcefully remove the link. Learn [how to recover a workspace in a soft-delete state](/azure/azure-monitor/logs/delete-workspace#recover-a-workspace-in-a-soft-delete-state) and [delete it permanently](/azure/azure-monitor/logs/delete-workspace#delete-a-workspace-permanently).
98
+
96
99
## Delete a shared capability Automation account
97
100
98
101
To delete your Automation account linked to a Log Analytics workspace in support of Update Management, Change Tracking and Inventory, and/or Start/Stop VMs during off-hours, perform the following steps.
Copy file name to clipboardExpand all lines: articles/backup/manage-backup-vault.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
@@ -2,7 +2,7 @@
2
2
title: Manage Backup vaults
3
3
description: Learn how to manage the Backup vaults.
4
4
ms.topic: how-to
5
-
ms.date: 10/10/2024
5
+
ms.date: 03/19/2025
6
6
ms.custom: references_regions
7
7
ms.service: azure-backup
8
8
author: jyothisuri
@@ -14,6 +14,8 @@ This article describes how to manage Backup vaults once they're created.
14
14
15
15
A Backup vault is a storage entity in Azure that houses backup data for certain newer workloads that Azure Backup supports. You can use Backup vaults to hold backup data for various Azure services, such Azure Database for PostgreSQL servers and newer workloads that Azure Backup will support. Backup vaults make it easy to organize your backup data, while minimizing management overhead. Backup vaults are based on the Azure Resource Manager model of Azure, which provides the **Azure role-based access control (Azure RBAC)** feature. Azure RBAC provides fine-grained access management control in Azure. [Azure provides various built-in roles](../role-based-access-control/built-in-roles.md), and Azure Backup has three [built-in roles to manage recovery points](backup-rbac-rs-vault.md). Backup vaults are compatible with Azure RBAC, which restricts backup and restore access to the defined set of user roles. [Learn more](backup-rbac-rs-vault.md).
16
16
17
+
Learn [how to create a Backup vault using Azure Business Continuity Center](../business-continuity-center/backup-vaults.md).
18
+
17
19
## Monitor and manage the Backup vault
18
20
19
21
This section explains how to use the Backup vault **Overview** dashboard to monitor and manage your Backup vaults. The overview pane contains two tiles: **Jobs** and **Instances**.
Copy file name to clipboardExpand all lines: articles/data-factory/connector-oracle.md
+23-23Lines changed: 23 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: jianleishen
6
6
ms.subservice: data-movement
7
7
ms.custom: synapse
8
8
ms.topic: conceptual
9
-
ms.date: 03/04/2025
9
+
ms.date: 03/20/2025
10
10
ms.author: jianleishen
11
11
---
12
12
@@ -32,7 +32,7 @@ For a list of data stores that are supported as sources or sinks by the copy act
32
32
33
33
Specifically, this Oracle connector supports:
34
34
35
-
- The following versions of an Oracle database for version 2.0:
35
+
- The following versions of an Oracle database for version 2.0 (Preview):
36
36
- Oracle Database 19c or later
37
37
- The following versions of an Oracle database for version 1.0:
38
38
- Oracle 19c R1 (19.1) and higher
@@ -86,14 +86,14 @@ The following sections provide details about properties that are used to define
86
86
87
87
## Linked service properties
88
88
89
-
The Oracle connector now supports version 2.0. Refer to this [section](#upgrade-the-oracle-connector) to upgrade your Oracle connector version from version 1.0. For the property details, see the corresponding sections.
89
+
The Oracle connector now supports version 2.0 (Preview). Refer to this [section](#upgrade-the-oracle-connector) to upgrade your Oracle connector version from version 1.0. For the property details, see the corresponding sections.
90
90
91
-
-[Version 2.0](#version-20)
91
+
-[Version 2.0 (Preview)](#version-20-preview)
92
92
-[Version 1.0](#version-10)
93
93
94
-
### Version 2.0
94
+
### Version 2.0 (Preview)
95
95
96
-
The Oracle linked service supports the following properties when apply version 2.0:
96
+
The Oracle linked service supports the following properties when apply version 2.0 (Preview):
97
97
98
98
| Property | Description | Required |
99
99
|:--- |:--- |:--- |
@@ -348,7 +348,7 @@ To copy data from Oracle, set the source type in the copy activity to `OracleSou
348
348
|:--- |:--- |:--- |
349
349
| type | The type property of the copy activity source must be set to `OracleSource`. | Yes |
350
350
| oracleReaderQuery | Use the custom SQL query to read data. An example is `"SELECT * FROM MyTable"`.<br>When you enable partitioned load, you need to hook any corresponding built-in partition parameters in your query. For examples, see the [Parallel copy from Oracle](#parallel-copy-from-oracle) section. | No |
351
-
| convertDecimalToInteger | Oracle NUMBER type with zero or unspecified scale will be converted to corresponding integer. Allowed values are **true** and **false** (default). <br>If you are using Oracle version 2.0, this property will only be allowed to be set when supportV1DataTypes is true. | No |
351
+
| convertDecimalToInteger | Oracle NUMBER type with zero or unspecified scale will be converted to corresponding integer. Allowed values are **true** and **false** (default). <br>If you are using Oracle version 2.0 (Preview), this property will only be allowed to be set when supportV1DataTypes is true. | No |
352
352
| partitionOptions | Specifies the data partitioning options used to load data from Oracle. <br>Allowed values are: **None** (default), **PhysicalPartitionsOfTable**, and **DynamicRange**.<br>When a partition option is enabled (that is, not `None`), the degree of parallelism to concurrently load data from an Oracle database is controlled by the [`parallelCopies`](copy-activity-performance-features.md#parallel-copy) setting on the copy activity. | No |
353
353
| partitionSettings | Specify the group of the settings for data partitioning. <br>Apply when the partition option isn't `None`. | No |
354
354
| partitionNames | The list of physical partitions that needs to be copied. <br>Apply when the partition option is `PhysicalPartitionsOfTable`. If you use a query to retrieve the source data, hook `?AdfTabularPartitionName` in the WHERE clause. For an example, see the [Parallel copy from Oracle](#parallel-copy-from-oracle) section. | No |
@@ -487,7 +487,7 @@ You are suggested to enable parallel copy with data partitioning especially when
487
487
488
488
When you copy data from and to Oracle, the following interim data type mappings are used within the service. To learn about how the copy activity maps the source schema and data type to the sink, see [Schema and data type mappings](copy-activity-schema-and-type-mapping.md).
489
489
490
-
| Oracle data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
490
+
| Oracle data type | Interim service data type (for version 2.0 (Preview)) | Interim service data type (for version 1.0) |
491
491
|:--- |:--- |:--- |
492
492
| BFILE |Byte[]| Byte[]|
493
493
| BINARY_FLOAT | Single | Single |
@@ -525,9 +525,9 @@ To learn details about the properties, check [Lookup activity](control-flow-look
525
525
526
526
Here are steps that help you upgrade the Oracle connector:
527
527
528
-
1. In **Edit linked service** page, select **2.0 (Preview)** under **Version** and configure the linked service by referring to [Linked service properties version 2.0](#version-20).
528
+
1. In **Edit linked service** page, select **2.0 (Preview)** under **Version** and configure the linked service by referring to [Linked service properties version 2.0 (Preview)](#version-20-preview).
529
529
530
-
For the authentication related properties including username and password, specify the original values in the corresponding fields in version 2.0. Other connection properties such as host, port, and Oracle Service Name/Oracle SID in version 1.0 are now parameters of the [`server` property in version 2.0](#server-property-configuration).
530
+
For the authentication related properties including username and password, specify the original values in the corresponding fields in version 2.0 (Preview). Other connection properties such as host, port, and Oracle Service Name/Oracle SID in version 1.0 are now parameters of the [`server` property in version 2.0 (Preview)](#server-property-configuration).
531
531
532
532
For example, if you configure the version 1.0 linked service as shown below:
533
533
@@ -549,7 +549,7 @@ Here are steps that help you upgrade the Oracle connector:
549
549
}
550
550
```
551
551
552
-
The identical version 2.0 linked service configuration using **Easy Connect (Plus) Naming** is:
552
+
The identical version 2.0 (Preview) linked service configuration using **Easy Connect (Plus) Naming** is:
553
553
554
554
:::image type="content" source="media/connector-oracle/easy-connect-naming-linked-service.png" alt-text="Screenshot of linked service using easy connector (Plus) naming.":::
555
555
@@ -573,7 +573,7 @@ Here are steps that help you upgrade the Oracle connector:
573
573
}
574
574
```
575
575
576
-
The identical version 2.0 linked service configuration using **Connector Descriptor** is:
576
+
The identical version 2.0 (Preview) linked service configuration using **Connector Descriptor** is:
577
577
578
578
:::image type="content" source="media/connector-oracle/connector-descriptor-linked-service.png" alt-text="Screenshot of linked service using connector descriptor.":::
579
579
@@ -603,13 +603,13 @@ Here are steps that help you upgrade the Oracle connector:
603
603
604
604
Note that:
605
605
606
-
- If you use **Oracle Service Name** in version 1.0, you can use **Easy Connect (Plus) Naming** or **Connector Descriptor** as the server format in version 2.0.
606
+
- If you use **Oracle Service Name** in version 1.0, you can use **Easy Connect (Plus) Naming** or **Connector Descriptor** as the server format in version 2.0 (Preview).
607
607
608
-
- If you use **Oracle SID** in version 1.0, you need to use **Connector Descriptor** as the server format in version 2.0.
608
+
- If you use **Oracle SID** in version 1.0, you need to use **Connector Descriptor** as the server format in version 2.0 (Preview).
609
609
610
-
- For some additional connection properties in version 1.0, we provide alternative properties or parameters in the `server` property in version 2.0. You can refer to the table below to upgrade the version 1.0 properties.
610
+
- For some additional connection properties in version 1.0, we provide alternative properties or parameters in the `server` property in version 2.0 (Preview). You can refer to the table below to upgrade the version 1.0 properties.
611
611
612
-
| Version 1.0 | Version 2.0 |
612
+
| Version 1.0 | Version 2.0 (Preview) |
613
613
|:--- |:--- |
614
614
| encryptionmethod| PROTOCOL (parameter in `server`) |
615
615
| tnsnamesfile | TNS_ADMIN (environment variable supported on the self-hosted integration runtime) |
@@ -625,7 +625,7 @@ Here are steps that help you upgrade the Oracle connector:
625
625
| cryptoprotocolversion | SSL_VERSION (parameter in `server`) |
626
626
| truststore | WALLET_LOCATION (parameter in `server`) |
627
627
628
-
For example, if you use `alternateservers` in version 1.0, you can set the `DESCRIPTION_LIST` parameter in the server property in version 2.0:
628
+
For example, if you use `alternateservers` in version 1.0, you can set the `DESCRIPTION_LIST` parameter in the server property in version 2.0 (Preview):
629
629
630
630
Version 1.0 linked service using `alternateservers`:
631
631
@@ -641,7 +641,7 @@ Here are steps that help you upgrade the Oracle connector:
641
641
}
642
642
```
643
643
644
-
Identical version 2.0 linked service using `DESCRIPTION_LIST` parameter in **Connector Descriptor**:
644
+
Identical version 2.0 (Preview) linked service using `DESCRIPTION_LIST` parameter in **Connector Descriptor**:
645
645
646
646
```json
647
647
{
@@ -659,15 +659,15 @@ Here are steps that help you upgrade the Oracle connector:
659
659
}
660
660
```
661
661
662
-
2. The data type mapping for the Oracle linked service version 2.0 is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Oracle](#data-type-mapping-for-oracle).
662
+
2. The data type mapping for the Oracle linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Oracle](#data-type-mapping-for-oracle).
663
663
664
-
An additional connection property `supportV1DataTypes` in version 2.0 can reduce upgrade difficulties caused by data type changes. Setting this property to `true` ensures that the data type in version 2.0 remains consistent with version 1.0.
664
+
An additional connection property `supportV1DataTypes` in version 2.0 (Preview) can reduce upgrade difficulties caused by data type changes. Setting this property to `true` ensures that the data type in version 2.0 (Preview) remains consistent with version 1.0.
665
665
666
-
## Differences between Oracle version 2.0 and version 1.0
666
+
## Differences between Oracle version 2.0 (Preview) and version 1.0
667
667
668
-
The Oracle connector version 2.0 offers new functionalities and is compatible with most features of version 1.0. The following table shows the feature differences between version 2.0 and version 1.0.
668
+
The Oracle connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The following table shows the feature differences between version 2.0 (Preview) and version 1.0.
669
669
670
-
| Version 2.0 | Version 1.0 |
670
+
| Version 2.0 (Preview) | Version 1.0 |
671
671
|:--- |:--- |
672
672
|The following mappings are used from Oracle data types to interim service data types used by the service internally. <br><br>NUMBER(p,s) -> Int16, Int32, Int64, Double, Single, Decimal <br>FLOAT(p)-> Double or Decimal based on its precision <br>NUMBER -> Decimal <br>TIMESTAMP WITH TIME ZONE -> DateTimeOffset <br>INTERVAL YEAR TO MONTH -> Int64 <br>INTERVAL DAY TO SECOND -> TimeSpan |The following mappings are used from Oracle data types to interim service data types used by the service internally. <br><br>NUMBER(p,s) -> Decimal or String based on its precision <br>FLOAT(p)-> Double <br>NUMBER -> Double <br>TIMESTAMP WITH TIME ZONE -> DateTime <br>INTERVAL YEAR TO MONTH -> String <br>INTERVAL DAY TO SECOND -> String |
673
673
| Support convertDecimalToInteger in copy source when `supportV1DataTypes` is set to `true`. | Support convertDecimalToInteger in copy source. |
0 commit comments