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
There are two versions of the solution: managed and unmanaged. We **strongly** recommend you use the managed version if importing into an existing environment with other solutions. If you want to customize the solution, you can use the unmanaged version or you can import that managed version and use an unmanaged solution to store your customiations.
2
+
3
+
## Word Template
4
+
Before you setup the solution, you must first load the Word template into a SharePoint document libray. You'll need to know the SharePoint site before importing the solution.
5
+
6
+
## Import Solution
7
+
8
+
There are two versions of the solution: managed and unmanaged. We **strongly** recommend you use the managed version if importing into an existing environment with other solutions. If you want to customize the solution, you can use the unmanaged version or you can import that managed version and use an unmanaged solution to store your customizations.
3
9
4
10
Which ever version you use, the steps are basically the same:
5
11
@@ -8,32 +14,41 @@ Which ever version you use, the steps are basically the same:
8
14
3. Click **Import Solution**
9
15
4. Click **Browse** and select the file (managed or unmanaged)
10
16
5. Click **Next**
11
-
6. You will be prompted to update the connections. If none exist, you will need to create them.
6. You will be prompted to update the connections. If none exist, you will need to create them.
18
+

13
19
14
-
7. When setting up the Azure Blob Storage connection, please set the follow parameters
8. When setting up the Azure Blob Storage connection, please set the follow parameters
21
+


28
+
22
29
9. Click **Next**
23
30
10. You will then be prompted to update the environment variables:
-**Speech to Text Region**: The Azure location/region used by the Azure Batch Speech to Text services
26
-
-**Speech to Text Key**: The key for the Azure Batch Speech to Text service
27
-
-**SharePoint Site**: The site where the SharePoint list is located
28
-
-**SharePoint List**: SharePoint list used to temporarily store the audio file as an attachment
29
-
-**Azure Blob Destination SAS URL**: The SAS URL for the container the the transcripts go into. _Note: this SAS URL must be configured for anonymous access and have write/create priviledges._
30
-
11. Click **Import**
31
+

32
+
33
+
-**Azure Speech to Text Region**: The Azure location/region used by the Azure Batch Speech to Text services
34
+
-**Azure Speech to Text Key**: The key for the Azure Batch Speech to Text service
35
+
-**Azure Blob Storage Source Container**: Path to the container that will receive the audio files
36
+
-**Azure Blob Destination SAS URL**: The SAS URL for the container the the transcripts go into. <br>_Note: this SAS URL must be configured for anonymous access and have write/create priviledges._
37
+
-**SharePoint Site**: The site where the Word document template is located
38
+
-**Web API Endpoint**: For Databverse Web API calls
If you do, you will need to go into the solution and turn on the parent flow (02 - Azure - When Audio File Created in Blob Storage - Create Transcript). This bug may be addressed in further releases.
44
+
## Update Flow with Word Template
45
+
46
+
Due to limitations with the Word connector, you must hard code the Word template into the [PA - Create Transcript Document](developer-guide.md#pa---create-transcript-document) flow
47
+
Edit the flow and update the **Document Library** and **File** parameters
Copy file name to clipboardExpand all lines: demos/transcript-demo-power+azure/readme.md
+15-8Lines changed: 15 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,7 @@
1
1
# Overview
2
-
This demo is designed to illustrate the "better together" story of Azure + Power Platform. The demo includes a canvas app that allows users to upload an audio file (MP3 or WAV) and then transcribe the audio and then edit the transcription (e.g. to fix discrepancies). Under the "hood", the solution leverages Power Automate flows to connect to Azure Blob Storage and Azure Speech Services to store and transcribe the audio respectively. The final output is then stored in Dataverse.
2
+
This demo is designed to illustrate the "better together" story of Azure + Power Platform. The demo includes a canvas app that allows users to upload an audio file and then transcribe the audio and then edit the transcription (e.g. to fix discrepancies). Under the "hood", the solution leverages Power Automate flows to connect to Azure Blob Storage and Azure Speech Services to store and transcribe the audio respectively. The final output is then stored in Dataverse.
3
3
4
-
5
-

4
+

6
5
7
6
# Contents
8
7
-[Release Notes](#release-notes)
@@ -20,6 +19,7 @@ This demo is designed to illustrate the "better together" story of Azure + Power
20
19
| Version | Release Date | Change Log |
21
20
| :------ | :---------- | :--------- |
22
21
| 1.0.1.0 | 3/21/2024 | - |
22
+
| 1.0.2.24 | 7/11/2024 | - Added GPT generated transcript summary (requires Generative AI enabled in environment) <br> - Added downloadable PDF transcript <br> - Removed SharePoint list dependency. App now uploades directly to Azure Blob Storage <br> - Other minor changes to UI/UX|
23
23
24
24
## Supported Clouds
25
25
This demo was built in a GCC-High tenant. If you are using a GCC tenant, note that you will need an Azure Gov subscription to connect directly to [Azure Blob Storage](https://powerautomate.microsoft.com/en-us/connectors/details/shared_azureblob/azure-blob-storage/) and [Azure Speech to Text](https://powerautomate.microsoft.com/en-us/connectors/details/shared_cognitiveservicesspe/azure-batch-speech-to-text/) from Power Apps and Power Automate via the out of the box (OOTB) connectors. There is a workaround described [here](https://github.com/microsoft/Federal-Business-Applications/wiki/PowerApps-Connecting-from-GCC-to-any-Endpoint-including-Commercial-Azure).
@@ -33,7 +33,8 @@ You must have the following to use this solution:
4.**Two**[Azure Blob Storage Containers](https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction) (source for audio and destination for transcripts)
35
35
5.[Azure Batch Speech to Text](https://learn.microsoft.com/en-us/azure/ai-services/speech-service/batch-transcription) key
36
-
6. SharePoint List with attachments enabled
36
+
6.[Generative AI Features enabled](https://github.com/microsoft/Federal-Business-Applications/blob/main/whitepapers/copilot/README.md#phase-1-opt-in-with-azure-commercial-azure-openai)
37
+
7. SharePoint Site & Document Library
37
38
38
39
[^ Top](#contents)
39
40
@@ -42,29 +43,35 @@ You must have the following to use this solution:
42
43
- Demo Transcript App (Canvas)
43
44
- Demo Transcript Admin App (Model Driven)
44
45
- Flows
45
-
- 01 - SPO - When Audio File Uploaded to SPO - Copy to Azure Blob
46
-
- 02 - Azure - When Audio File Created in Blob Storage - Create Transcript
46
+
- 01 - Power Apps - Upload to Azure Blob
47
+
- 02 - Azure - Create Transcript
47
48
- 02b Child Flow - Loop Until Transcript is Complete
48
49
- 02c Child Flow - Get Transcript Results
49
50
- 02d Child Flow - Parse Transcript and Load into a Dataverse
51
+
- 02e Child Flow - Summarize Transcript
52
+
- PA - Create Transcript Document
50
53
- Tables
51
54
- Transcripts
52
55
- Recogonized Phrases
53
-
-Transcript
56
+
-Speakers
54
57
- Environment Variables - *Note: these will need to be updated on import*
55
58
- SharePoint Site
56
-
- SharePoint List
57
59
- Speech to Text Key
58
60
- Speech to Text Region
59
61
- Azure Blob Destination SAS URL
60
62
-*note: this requires a SAS URI be generated and the container must allow for anonmyous access. Additional info, and other more secure methods are described [here](https://learn.microsoft.com/en-us/azure/ai-services/speech-service/batch-transcription-create?pivots=rest-api#specify-a-destination-container-url)*
63
+
- Web API Endpoint
64
+
- Azure Blob Storage Source Container
61
65
- Web Resources
62
66
- Icons for each table
63
67
- Connection References - *Note: these will need to be updated on import*
0 commit comments