To answer your specific questions directly:
1. An M365 Group-connected SharePoint site CAN be used as a content source for Power Pages, but not natively as a built-in knowledge/content feed. You integrate SharePoint content into Power Pages via Power Automate flows (sync content to Dataverse), SharePoint connector, or embedded SharePoint document library components via iframes or web part-style embedding. There's no direct SharePoint-to-Power Pages content pipeline.
2. No. Power Pages is created and managed from the Power Platform admin center or make.powerpages.microsoft.com, not from a SharePoint site. The M365 Group-connected SharePoint site has no Power Pages management capability built in.
3. A Communication Site is the right SharePoint approach for your scenario, not an M365 Group-connected team site. Communication sites are designed for organization-wide publishing (broad audience, read-mostly) while M365 Group sites are designed for team collaboration. For file sharing across the org, Communication Site is the recommendation.
4. The confirmed integration methods between SharePoint and Power Pages are: Power Automate flows to sync or push SharePoint content into Dataverse tables (which Power Pages reads natively), the SharePoint connector in Power Automate, or Microsoft Graph API for more custom scenarios. For displaying SharePoint documents in a Power Pages portal, you can also use the SharePoint document library component available in Power Pages design studio.
Recommended architecture for your goal: Communication Site for file sharing + dedicated Power Platform environment with Power Pages for the portal + Dataverse for structured content + Power Automate to sync or integrate as needed.
Best regards,
Valantis
✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.
❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).
🏷️ For follow-ups @Valantis.
📝 https://valantisond365.com/