Skip to content

Commit ac9f6d5

Browse files
committed
change a Azure to an Azure
1 parent 306f8c0 commit ac9f6d5

18 files changed

+38
-38
lines changed

articles/data-factory/connector-oracle-cloud-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Copy data from Oracle Cloud Storage
3-
description: Learn about how to copy data from Oracle Cloud Storage to supported sink data stores using a Azure Data Factory or Synapse Analytics pipeline.
3+
description: Learn about how to copy data from Oracle Cloud Storage to supported sink data stores using an Azure Data Factory or Synapse Analytics pipeline.
44
titleSuffix: Azure Data Factory & Azure Synapse
55
author: jianleishen
66
ms.service: data-factory

articles/energy-data-services/faq-energy-data-services.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ sections:
5252
answer: >
5353
Azure Data Manager for Energy Preview is a fully managed OSDU™ Data Platform. It means that the underlying infrastructure, security updates, new features, and upgrade to new OSDU™ versions is fully managed by Microsoft.
5454
55-
- question: Can I move a Azure Data Manager for Energy Preview resource from one subscription or resource group to another?
55+
- question: Can I move an Azure Data Manager for Energy Preview resource from one subscription or resource group to another?
5656
answer: >
57-
Today, you can't move a Azure Data Manager for Energy Preview resource from one subscription or resource group to another. Instead you can, delete the existing Azure Data Manager for Energy Preview instance in the current resource group or subscription. Create a new Azure Data Manager for Energy Preview instance in the target resource group or subscription. Next, reingest the data into the new Microsoft Energy Data Service instance.
57+
Today, you can't move an Azure Data Manager for Energy Preview resource from one subscription or resource group to another. Instead you can, delete the existing Azure Data Manager for Energy Preview instance in the current resource group or subscription. Create a new Azure Data Manager for Energy Preview instance in the target resource group or subscription. Next, reingest the data into the new Microsoft Energy Data Service instance.
5858

articles/energy-data-services/how-to-add-more-data-partitions.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,24 +18,24 @@ In this article, you'll learn how to add data partitions to an existing Azure Da
1818
Each partition provides the highest level of data isolation within a single deployment. All access rights are governed at a partition level. Data is separated in a way that allows for the partition's life cycle and deployment to be handled independently. (See [Partition Service](https://community.opengroup.org/osdu/platform/home/-/issues/31) in OSDU™)
1919

2020

21-
You can create maximum five data partitions in one MEDS instance. Currently, in line with the data partition capabilities that are available in OSDU™, you can only create data partitions but can't delete or rename data existing data partitions.
21+
You can create maximum five data partitions in one Azure Data Manager for Energy instance. Currently, in line with the data partition capabilities that are available in OSDU™, you can only create data partitions but can't delete or rename data existing data partitions.
2222

2323

2424
## Create a data partition
2525

26-
1. Open the "Data Partitions" menu-item from left-panel of MEDS overview page.
26+
1. Open the "Data Partitions" menu-item from left-panel of Azure Data Manager for Energy overview page.
2727

28-
[![Screenshot for dynamic data partitions feature discovery from MEDS overview page. Find it under the 'advanced' section in menu-items.](media/how-to-add-more-data-partitions/dynamic-data-partitions-discovery-meds-overview-page.png)](media/how-to-add-more-data-partitions/dynamic-data-partitions-discovery-meds-overview-page.png#lightbox)
28+
[![Screenshot for dynamic data partitions feature discovery from Azure Data Manager for Energy overview page. Find it under the 'advanced' section in menu-items.](media/how-to-add-more-data-partitions/dynamic-data-partitions-discovery-meds-overview-page.png)](media/how-to-add-more-data-partitions/dynamic-data-partitions-discovery-meds-overview-page.png#lightbox)
2929

3030
2. Select "Create".
3131

32-
The page shows a table of all data partitions in your MEDS instance with the status of the data partition next to it. Clicking the "Create" option on the top opens a right-pane for next steps.
32+
The page shows a table of all data partitions in your Azure Data Manager for Energy instance with the status of the data partition next to it. Clicking the "Create" option on the top opens a right-pane for next steps.
3333

3434
[![Screenshot to help you locate the create button on the data partitions page. The 'create' button to add a new data partition is highlighted.](media/how-to-add-more-data-partitions/start-create-data-partition.png)](media/how-to-add-more-data-partitions/start-create-data-partition.png#lightbox)
3535

3636
3. Choose a name for your data partition.
3737

38-
Each data partition name needs to be 1-10 characters long and be a combination of lowercase letters, numbers and hyphens only. The data partition name will be prepended with the name of the MEDS instance. Choose a name for your data partition and hit create. As soon as you hit create, the deployment of the underlying data partition resources such as Azure Cosmos DB and Azure Storage accounts is started.
38+
Each data partition name needs to be 1-10 characters long and be a combination of lowercase letters, numbers and hyphens only. The data partition name will be prepended with the name of the Azure Data Manager for Energy instance. Choose a name for your data partition and hit create. As soon as you hit create, the deployment of the underlying data partition resources such as Azure Cosmos DB and Azure Storage accounts is started.
3939

4040
>[!NOTE]
4141
>It generally takes 15-20 minutes to create a data partition.

articles/energy-data-services/how-to-convert-segy-to-ovds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In this article, you will learn how to convert SEG-Y formatted data to the Open
2121

2222
1. Download and install [Postman](https://www.postman.com/) desktop app.
2323
2. Import the [oVDS Conversions.postman_collection](https://community.opengroup.org/osdu/platform/pre-shipping/-/blob/main/R3-M9/Azure-M9/Services/DDMS/oVDS_Conversions.postman_collection.json) into Postman. All curl commands used below are added to this collection. Update your Environment file accordingly
24-
3. Ensure that a Azure Data Manager for Energy Preview instance is created already
24+
3. Ensure that an Azure Data Manager for Energy Preview instance is created already
2525
4. Clone the **sdutil** repo as shown below:
2626

2727
```markdown

articles/energy-data-services/how-to-manage-data-security-and-encryption.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -79,14 +79,14 @@ In addition to TLS, when you interact with Azure Data Manager for Energy Preview
7979

8080
12. Next, select “**Review+Create**” after completing other tabs.
8181
13. Select the "**Create**" button.
82-
14. A Azure Data Manager for Energy Preview instance is created with customer-managed keys.
82+
14. an Azure Data Manager for Energy Preview instance is created with customer-managed keys.
8383
15. Once CMK is enabled you will see its status on the **Overview** screen.
8484

85-
[![Screenshot of CMK enabled on MEDS overview page](media/how-to-manage-data-security-and-encryption/customer-managed-key-6-cmk-enabled-meds-overview.png)](media/how-to-manage-data-security-and-encryption/customer-managed-key-6-cmk-enabled-meds-overview.png#lightbox)
85+
[![Screenshot of CMK enabled on Azure Data Manager for Energy overview page](media/how-to-manage-data-security-and-encryption/customer-managed-key-6-cmk-enabled-meds-overview.png)](media/how-to-manage-data-security-and-encryption/customer-managed-key-6-cmk-enabled-meds-overview.png#lightbox)
8686

8787
16. You can navigate to **Encryption** and see that CMK enabled with user managed identity.
8888

89-
[![Screenshot of CMK settings disabled once MEDS instance is installed](media/how-to-manage-data-security-and-encryption/customer-managed-key-7-cmk-disabled-meds-instance-created.png)](media/how-to-manage-data-security-and-encryption/customer-managed-key-7-cmk-disabled-meds-instance-created.png#lightbox)
89+
[![Screenshot of CMK settings disabled once Azure Data Manager for Energy instance is installed](media/how-to-manage-data-security-and-encryption/customer-managed-key-7-cmk-disabled-meds-instance-created.png)](media/how-to-manage-data-security-and-encryption/customer-managed-key-7-cmk-disabled-meds-instance-created.png#lightbox)
9090

9191

9292

articles/energy-data-services/how-to-manage-legal-tags.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Run the below curl command in Azure Cloud Bash to create a legal tag for a given
4242
```
4343

4444
### Sample request
45-
Consider a Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
45+
Consider an Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
4646

4747
```bash
4848
curl --location --request POST 'https://medstest.energy.azure.com/api/legal/v1/legaltags' \
@@ -144,7 +144,7 @@ Run the below curl command in Azure Cloud Bash to get the legal tag associated w
144144
```
145145

146146
### Sample request
147-
Consider a Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
147+
Consider an Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
148148

149149
```bash
150150
curl --location --request GET 'https://medstest.energy.azure.com/api/legal/v1/legaltags/medstest-dp1-legal-tag' \

articles/energy-data-services/how-to-manage-users.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ In this article, you'll know how to manage users in Azure Data Manager for Energ
1616

1717
## Prerequisites
1818

19-
Create a Azure Data Manager for Energy Preview instance using the tutorial at [How to create Azure Data Manager for Energy Preview instance](quickstart-create-microsoft-energy-data-services-instance.md).
19+
Create an Azure Data Manager for Energy Preview instance using the tutorial at [How to create Azure Data Manager for Energy Preview instance](quickstart-create-microsoft-energy-data-services-instance.md).
2020

2121
You will need to pass parameters for generating the access token, which you'll need to make valid calls to the Entitlements API of your Azure Data Manager for Energy Preview instance. You will also need these parameters for different user management requests to the Entitlements API. Hence Keep the following values handy for these actions.
2222

@@ -125,7 +125,7 @@ The value to be sent for the param **"email"** is the **Object_ID (OID)** of the
125125

126126
**Sample request**
127127

128-
Consider a Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
128+
Consider an Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
129129

130130
```bash
131131
curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/[email protected]/members' \
@@ -165,7 +165,7 @@ The value to be sent for the param **"email"** is the **Object_ID (OID)** of the
165165

166166
**Sample request**
167167

168-
Consider a Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
168+
Consider an Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
169169

170170
```bash
171171
curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/[email protected]/members' \
@@ -199,7 +199,7 @@ Run the below curl command in Azure Cloud Bash to get all the groups associated
199199

200200
**Sample request**
201201

202-
Consider a Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
202+
Consider an Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
203203

204204
```bash
205205
curl --location --request GET 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX/groups?type=none' \
@@ -241,7 +241,7 @@ As stated above, **DO NOT** delete the OWNER of a group unless you have another
241241

242242
**Sample request**
243243

244-
Consider a Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
244+
Consider an Azure Data Manager for Energy Preview instance named "medstest" with a data partition named "dp1"
245245

246246
```bash
247247
curl --location --request DELETE 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX' \

articles/energy-data-services/how-to-set-up-private-links.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ ms.custom: template-how-to
1313
# Create a private endpoint for Azure Data Manager for Energy Preview
1414
[Azure Private Link](../private-link/private-link-overview.md) provides private connectivity from a virtual network to Azure platform as a service (PaaS). It simplifies the network architecture and secures the connection between endpoints in Azure by eliminating data exposure to the public internet.
1515

16-
By using Azure Private Link, you can connect to a Azure Data Manager for Energy Preview instance from your virtual network via a private endpoint, which is a set of private IP addresses in a subnet within the virtual network. You can then limit access to your Azure Data Manager for Energy Preview instance over these private IP addresses.
16+
By using Azure Private Link, you can connect to an Azure Data Manager for Energy Preview instance from your virtual network via a private endpoint, which is a set of private IP addresses in a subnet within the virtual network. You can then limit access to your Azure Data Manager for Energy Preview instance over these private IP addresses.
1717

18-
You can connect to a Azure Data Manager for Energy Preview instance that's configured with Private Link by using an automatic or manual approval method. To learn more, see the [Private Link documentation](../private-link/private-endpoint-overview.md#access-to-a-private-link-resource-using-approval-workflow).
18+
You can connect to an Azure Data Manager for Energy Preview instance that's configured with Private Link by using an automatic or manual approval method. To learn more, see the [Private Link documentation](../private-link/private-endpoint-overview.md#access-to-a-private-link-resource-using-approval-workflow).
1919

2020
This article describes how to set up a private endpoint for Azure Data Manager for Energy Preview.
2121

@@ -29,7 +29,7 @@ This article describes how to set up a private endpoint for Azure Data Manager f
2929

3030
Use the following steps to create a private endpoint for an existing Azure Data Manager for Energy Preview instance by using the Azure portal:
3131

32-
1. From the **All resources** pane, choose a Azure Data Manager for Energy Preview instance.
32+
1. From the **All resources** pane, choose an Azure Data Manager for Energy Preview instance.
3333
1. Select **Networking** from the list of settings.
3434
1. On the **Public Access** tab, select **Enabled from all networks** to allow traffic from all networks.
3535

articles/energy-data-services/quickstart-create-microsoft-energy-data-services-instance.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Create a Microsoft Azure Data Manager for Energy Preview instance #Required; page title is displayed in search results. Include the brand.
3-
description: Quickly create a Azure Data Manager for Energy Preview instance #Required; article description that is displayed in search results.
3+
description: Quickly create an Azure Data Manager for Energy Preview instance #Required; article description that is displayed in search results.
44
author: nitinnms #Required; your GitHub user alias, with correct capitalization.
55
ms.author: nitindwivedi #Required; microsoft alias of author; optional team alias.
66
ms.service: energy-data-services #Required; service per approved list. slug assigned by ACOM.
@@ -9,11 +9,11 @@ ms.date: 08/18/2022
99
ms.custom: template-quickstart #Required; leave this attribute/value as-is.
1010
---
1111

12-
# Quickstart: Create a Azure Data Manager for Energy Preview Preview instance
12+
# Quickstart: Create an Azure Data Manager for Energy Preview Preview instance
1313

1414
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
1515

16-
Get started by creating a Azure Data Manager for Energy Preview instance on Azure portal on a web browser. You first register an Azure application on Active Directory and then use the application ID to create a Azure Data Manager for Energy Preview instance in your chosen Azure Subscription and region.
16+
Get started by creating an Azure Data Manager for Energy Preview instance on Azure portal on a web browser. You first register an Azure application on Active Directory and then use the application ID to create an Azure Data Manager for Energy Preview instance in your chosen Azure Subscription and region.
1717

1818
The setup of Azure Data Manager for Energy Preview instance can be triggered using a simple interface on Azure portal and takes about 50 minutes to complete.
1919

@@ -28,7 +28,7 @@ Application ID | You'll need an [application ID](../active-directory/develop/app
2828
Client Secret | Sometimes called an application password, a client secret is a string value that your app can use in place of a certificate to identity itself. You can [create a client secret](../active-directory/develop/quickstart-register-app.md#add-a-client-secret) by selecting *Certificates & secrets* > *Client secrets* > *New client secret*. Record the secret's value for use in your client application code. This secret value is never displayed again after you leave this page.
2929

3030

31-
## Create a Azure Data Manager for Energy Preview instance
31+
## Create an Azure Data Manager for Energy Preview instance
3232

3333

3434
1. Save your **Application (client) ID** and **client secret** from Azure Active Directory to refer to them later in this quickstart.
@@ -92,9 +92,9 @@ Client Secret | Sometimes called an application password, a client secret is a s
9292
[![Screenshot of the overview of Azure Data Manager for Energy Preview instance page. Details as such data partitions, instance URI, and app ID are accessible.](media/quickstart-create-microsoft-energy-data-services-instance/overview-energy-data-services.png)](media/quickstart-create-microsoft-energy-data-services-instance/overview-energy-data-services.png#lightbox)
9393

9494

95-
## Delete a Azure Data Manager for Energy Preview instance
95+
## Delete an Azure Data Manager for Energy Preview instance
9696

97-
Deleting a Microsoft Energy Data instance also deletes any data that you've ingested. This action is permanent and the ingested data can't be recovered. To delete a Azure Data Manager for Energy Preview instance, complete the following steps:
97+
Deleting a Microsoft Energy Data instance also deletes any data that you've ingested. This action is permanent and the ingested data can't be recovered. To delete an Azure Data Manager for Energy Preview instance, complete the following steps:
9898

9999
1. Sign in to the Azure portal and delete the *resource group* in which these components are installed.
100100

@@ -103,6 +103,6 @@ Deleting a Microsoft Energy Data instance also deletes any data that you've inge
103103
OSDU™ is a trademark of The Open Group.
104104

105105
## Next steps
106-
After provisioning a Azure Data Manager for Energy Preview instance, you can learn about user management on this instance.
106+
After provisioning an Azure Data Manager for Energy Preview instance, you can learn about user management on this instance.
107107
> [!div class="nextstepaction"]
108108
> [How to manage users](how-to-manage-users.md)

0 commit comments

Comments
 (0)