Designing a Power Automate flow for Word/PDF intake → SharePoint routing — do AI agents actually cost money?
Designing a Power Automate flow for Word/PDF intake → SharePoint routing — do AI agents actually cost money?
Designing a Power Automate flow for Word/PDF intake → SharePoint routing — do AI agents actually cost money?
Re: Designing a Power Automate flow for Word/PDF intake → SharePoint routing — do AI agents actually cost money?
Ok.
Yes, AI Text extraction is pay as you go.
Pay-as-you-go pricing for document processing for Microsoft 365 | Microsoft Learn https://share.google/R9ThjCsSolF24y6Uk
You can use auto fill columns or document processing for this and don't necessarily require AI Credits.
Instead of storing the docs to OneDrive and then the extracted info in a separate Sharepoint list, you can save the doc directly to Sharepoint and have the extraction logic applied as part of the Sharepoint library level auto fill or document processing.
If you use case requires the AI extraction to be done in Power Automate and cannot be handed off to Sharepoint, then you will use Copilot Studio credits(AI builder credits are being deprecated).
Reading your description, I think you may be able to handle the extraction part outside the flow with a dedicated Sharepoint library.
Another solid option is leveraging Azure Document Intelligence, much lower pricing than using copilot credits, but requires some extra steps. Totally worth the extra steps especially if there's going to be volume.
Yes, AI Text extraction is pay as you go.
Pay-as-you-go pricing for document processing for Microsoft 365 | Microsoft Learn https://share.google/R9ThjCsSolF24y6Uk
You can use auto fill columns or document processing for this and don't necessarily require AI Credits.
Instead of storing the docs to OneDrive and then the extracted info in a separate Sharepoint list, you can save the doc directly to Sharepoint and have the extraction logic applied as part of the Sharepoint library level auto fill or document processing.
If you use case requires the AI extraction to be done in Power Automate and cannot be handed off to Sharepoint, then you will use Copilot Studio credits(AI builder credits are being deprecated).
Reading your description, I think you may be able to handle the extraction part outside the flow with a dedicated Sharepoint library.
Another solid option is leveraging Azure Document Intelligence, much lower pricing than using copilot credits, but requires some extra steps. Totally worth the extra steps especially if there's going to be volume.