Here are the options I would like to suggest:
Web Resources (your current idea)
Storing GeoJSON in web resources works, but it has trade-offs. Web resources are versioned with your solution, so updates require a new deployment. For static geographic data that rarely changes, this is fine. For anything you update frequently, it becomes painful.
SharePoint Document Library
If your environment has SharePoint, store the GeoJSON files there and fetch them via the SharePoint REST API or Microsoft Graph. You get versioning, access control, and easy file replacement without touching your solution. The downside is an extra authentication hop from your canvas app or PCF component.
Dataverse File Column or Note Attachment
You can store binary/JSON content in a Dataverse file column or as an annotation attachment. Query it like any other Dataverse record. This keeps everything inside the platform and works well if you need row-level security on the data.
Azure Blob Storage
If you control an Azure subscription tied to this tenant, a blob with public read access (or SAS token) gives you a CDN-backed, easily updatable file store. Your generative page fetches it like any external URL, but now you own it.
Thank you!
Proud to be a Super User!
🏷️ Need more help?
✅ Don’t forget to Accept as Solution if this guidance worked for you.
❤️Your Like motivates me to keep helping
