Skip to content

Commit ebf67aa

Browse files
committed
edit pass: data-manager-for-agri-concepts
1 parent 1989cdb commit ebf67aa

File tree

2 files changed

+73
-50
lines changed

2 files changed

+73
-50
lines changed

articles/data-manager-for-agri/concepts-llm-apis.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Using generative AI in Data Manager for Agriculture
3-
description: Provides information on using generative AI feature in Azure Data Manager for Agriculture
2+
title: Generative AI in Azure Data Manager for Agriculture
3+
description: Learn how to use generative AI features in Azure Data Manager for Agriculture.
44
author: gourdsay
55
ms.author: angour
66
ms.service: data-manager-for-agri
@@ -9,41 +9,41 @@ ms.date: 3/19/2024
99
ms.custom: template-concept
1010
---
1111

12-
# Generative AI in Data Manager for Agriculture
12+
# Generative AI in Azure Data Manager for Agriculture
1313

14-
The copilot templates for agriculture enable seamless retrieval of data stored in Data Manager for Agriculture so that farming-related context and insights can be queried in conversational context. These capabilities enable customers and partners to build their own agriculture copilots.
14+
The copilot templates for agriculture enable seamless retrieval of data stored in Azure Data Manager for Agriculture so that farming-related context and insights can be queried in a conversational context. These capabilities enable customers and partners to build their own agriculture copilots.
1515

16-
Customers and partners can deliver insights to users around disease, yield, harvest windows and more, using actual planning, and observational data. While Data Manager for Agriculture isn't required to operationalize copilot templates for agriculture, the Data Manager enables customers to more easily integrate generative AI scenarios for their users.
16+
Customers and partners can deliver insights to users around disease, yield, harvest windows, and more, by using actual planning and observational data. Although Azure Data Manager for Agriculture isn't required to operationalize copilot templates for agriculture, it enables customers to more easily integrate generative AI scenarios for their users.
1717

18-
Many customers have proprietary data outside of our data manager, for example Agronomy PDFs, market price data etc. These customers can benefit from our orchestration framework that allows for plugins, embedded data structures, and sub processes to be selected as part of the query flow.
18+
Many customers have proprietary data outside Azure Data Manager for Agriculture; for example, agronomy PDFs or market price data. These customers can benefit from an orchestration framework that allows for plugins, embedded data structures, and subprocesses to be selected as part of the query flow.
1919

20-
Customers with farm operations data in our data manager can use our plugins that enable seamless selection of APIs mapped to farm operations today. In the time to come we'll add the capability to select APIs mapped to soil sensors, weather, and imagery type of data. Our data manager focused plugin allows for a combination of results, calculation of area, ranking, summarizing to help serve customer prompts.
20+
Customers who have farm operations data in Azure Data Manager for Agriculture can use plugins that enable seamless selection of APIs mapped to farm operations. These plugins allow for a combination of results, calculation of area, ranking, and summarizing to help serve customer prompts.
2121

22-
Our copilot templates for agriculture make generative AI in agriculture a reality.
22+
The copilot templates for agriculture make generative AI in agriculture a reality.
2323

2424
> [!NOTE]
25-
> Azure might include preview, beta, or other prerelease features, services, software, or regions offered by Microsoft for optional evaluation. Previews are licensed to you as part of [your agreement](https://azure.microsoft.com/support) governing use of Azure, and are subject to terms applicable to previews.
25+
> Azure might include preview, beta, or other prerelease features, services, software, or regions offered by Microsoft for optional evaluation. Previews are licensed to you as part of [your agreement](https://azure.microsoft.com/support) governing the use of Azure, and are subject to terms applicable to previews.
2626
>
2727
> The preview of Azure Data Manager for Agriculture and related Microsoft generative AI services are subject to [additional terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). These additional terms supplement your agreement governing your use of Azure. If you don't agree to these terms, don't use the previews.
2828
2929
## Prerequisites
3030

3131
- An instance of [Azure Data Manager for Agriculture](quickstart-install-data-manager-for-agriculture.md)
32-
- An instance of [Azure OpenAI](../ai-services/openai/how-to/create-resource.md) created in your Azure subscription
33-
- You need [Azure Key Vault](../key-vault/general/quick-create-portal.md)
34-
- You need [Azure Container Registry](../container-registry/container-registry-get-started-portal.md)
32+
- An instance of [Azure OpenAI Service](../ai-services/openai/how-to/create-resource.md) created in your Azure subscription
33+
- [Azure Key Vault](../key-vault/general/quick-create-portal.md)
34+
- [Azure Container Registry](../container-registry/container-registry-get-started-portal.md)
3535

3636
## High-level architecture
3737

38-
The customer has full control as key component deployment is within the customer tenant. Our feature is available to customers via a docker container, which needs to be deployed to the customers Azure App Service.
38+
You have full control because deployment of key components is within your tenant. The copilot templates for agriculture are available via a Docker container, which is deployed to your Azure App Service instance.
3939

40-
:::image type="content" source="./media/concepts-llm-apis/high-level-architecture.png" alt-text="Screenshot showing high level feature architecture.":::
40+
:::image type="content" source="./media/concepts-llm-apis/high-level-architecture.png" alt-text="Screenshot that shows the high-level feature architecture.":::
4141

42-
We recommend that you apply content and safety filters on your Azure OpenAI instance. Taking this step ensures that the generative AI capability is aligned with guidelines from Microsoft's Office of Responsible AI. Follow instructions on how to use content filters with Azure OpenAI service at this [link](../ai-services/openai/how-to/content-filters.md) to get started.
42+
We recommend that you apply content and safety filters on your Azure OpenAI instance. Taking this step helps ensure that the generative AI capability is aligned with guidelines from Microsoft's Office of Responsible AI. To get started, follow the [instructions on how to use content filters with Azure OpenAI](../ai-services/openai/how-to/content-filters.md).
4343

44-
## Current farm operations related uses cases
44+
## Use cases for farm operations
4545

46-
We support seamless selection of APIs mapped to farm operations today. This enables use cases that are based on tillage, planting, applications, and harvesting type of farm operations. Here's a sample list of queries that you can test and use:
46+
Azure Data Manager for Agriculture supports seamless selection of APIs mapped to farm operations. This support enables use cases that are based on tillage, planting, applications, and harvesting types of farm operations. Here's a sample list of queries that you can test and use:
4747

4848
- Show me active fields
4949
- What crop was planted in my field (use field name)
@@ -57,7 +57,7 @@ We support seamless selection of APIs mapped to farm operations today. This enab
5757
- What is the average yield for my field (use field name) with crop (use crop name)
5858
- What is the effect of planting dates on yield for crop (use crop name)
5959

60-
These use cases help input providers to plan equipment, seeds, applications, and related services and engage better with the farmer.
60+
These use cases can help input providers to plan equipment, seeds, applications, and related services and engage better with the farmer.
6161

6262
## Next steps
6363

0 commit comments

Comments
 (0)