PowerShell Script — Microsoft Graph API Auto-Upload to SharePoint with Metadata Tagging

**Title:** PowerShell Script — Microsoft Graph API Auto-Upload to SharePoint with Metadata Tagging **Budget:** $400–$600 fixed price --- **Overview** We are a CPA firm (New York, 15 staff) running a shared Windows Server terminal environment. We need a PowerShell script that watches a folder (C:\Transit) on the VM, parses a structured filename, auto-tags SharePoint metadata columns, and uploads the file to a SharePoint document library — entirely replacing manual browser-based tagging. A detailed technical specification document (14-section RFP) is available immediately upon engagement. --- **What the Script Does** 1. Monitors C:\Transit on the Windows Server VM using a FileSystemWatcher or Task Scheduler loop 2. When a new PDF appears, parses the filename using this convention: - Format: [ClientCode][TypeLetter][Period][F] - Example: SAND4521E2025F — 8-char client code + 1-char document type + 4 or 6-char period + optional F (Final flag) 3. Looks up the full Account name from Microsoft Dynamics 365 using the 8-character ClientCode (via Graph API or D365 REST API) 4. Uploads the file to a SharePoint Online document library via Microsoft Graph API 5. Auto-populates 5 SharePoint metadata columns: Account (text), Document Type (choice), Period (text), Status (Draft or Final), Contact (blank — leave empty) 6. Moves the processed file out of C:\Transit and logs the result 7. Sends an alert email on any failure --- **Tech Stack** - Windows Server (hosted VM) - PowerShell 5.1 or 7 - Microsoft Graph API (SharePoint + D365 endpoints) - Entra ID app registration (client credentials flow) — we will create and provide client ID, tenant ID, and client secret - SharePoint Online — Microsoft 365 Business Basic tenant - Dynamics 365 — for ClientCode → Account name lookup --- **Deliverables** 1. Fully tested PowerShell script (.ps1) with inline comments 2. Entra app registration setup guide (what permissions to request) 3. Deployment instructions for Windows Task Scheduler or Windows Service 4. Error log format and alert email configuration 5. One supervised screen-share session to deploy to production --- **Access and Security** - Development and testing must use a test SharePoint library and dummy files — no real client data during build - Production deployment via one supervised screen-share session (firm principal present throughout) - Developer never holds credentials — all credential entry done by firm principal during session - Deliverable is the script file and documentation — not ongoing VM access --- **Budget** Fixed price: $400–$600. Proposals significantly outside this range without clear justification will not be considered. Please do not apply if you need more than 2 weeks to deliver. --- **How to Apply** Please include: - Brief description of your PowerShell and Microsoft Graph API experience - Examples of similar SharePoint/Graph API projects you have delivered - Fixed-price quote for this scope - Estimated delivery timeline - Any questions about the specification A detailed 14-section technical RFP is ready to share immediately. This is a well-defined, one-time project — no ambiguity in the spec.