Automated delivery of engine outputs from the data platform into SharePoint, announced in Teams, with a return leg for reviewer edits.
Every report cycle meant the same routine. Someone downloaded workbooks from the data platform. Someone uploaded them to SharePoint by hand. Then reviewer edits came back the same way, collected file by file.
The engine was doing the hard work. A person was still carrying its output around.
A pipeline built on a service principal, so it runs as a system identity rather than a person's login. Workbooks travel from the platform to a staging folder automatically. On a decision, they publish to the live folders, and Teams announces them.
The return leg is covered too. Reviewer edits travel back into the platform before the next run, and every file is archived on the way.
Proven end to end on the first live run. Workbooks left the platform, published to the live folders, and were announced in Teams with no hands on any file.
One manual step remains. Someone still starts the engine. That step disappears the moment the platform grants scheduled job rights.
Nobody downloads or uploads a report anymore.
Reports that still travel by hand? We build pipelines that deliver the files, announce them, and bring the edits back.