Size increase of .sppkg packages with heft/v1.22
After upgrading our solution to SPFx 1.22.rc-0 and switching to the new heft build toolchain our .sppkg packages have suddenly grown massively in size. They are more than double the size of the 1.21 version. Is there a reason for this? Is there anything we can do to reduce the package size back to what it was previously? Our main solution contains both web parts and list extensions, split into several bundles. Let me know what other details would be helpful.Microsoft 365 & Power Platform Community call - Community demos
💡 Microsoft 365 & Power Platform Development bi-weekly community call focuses on different use cases and features within the Microsoft 365 and Power Platform - across Microsoft 365 Copilot, Copilot Studio, SharePoint, Power Apps and more. 👏 Looking to catch up on the latest news and updates, including cool community demos, this call is for you! 📅 On 18th of December we'll have following agenda: Copilot prompt of the week CommunityDays.org update Microsoft 365 Maturity Model update Latest on PnP Framework and Core SDK extension Latest on PnP PowerShell Latest on Copilot pro dev samples Latest on Power Platform samples Picture time with the Together Mode! Mike Givens (CACI) Automating smart Approval cancellations in Power Automate with Dataverse Ben Fetters (Peak Power Apps) – Creating a comments section in Canvas Apps with JSON Ejaz Hussain (Advania UK) – Integrate Copilot Agents into SharePoint: OOTB and Programmatic Approaches (Client API & WebChat) 📅 Download recurrent invite from https://aka.ms/community/m365-powerplat-dev-call-invite 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/m365-powerplat-dev-call-join 👋 See you in the call! 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!Microsoft 365 & Power Platform product updates call
💡Microsoft 365 & Power Platform product updates call concentrates on the different use cases and features within the Microsoft 365 and in Power Platform. Call includes topics like Microsoft 365 Copilot, Copilot Studio, Microsoft Teams, Power Platform, Microsoft Graph, Microsoft Viva, Microsoft Search, Microsoft Lists, SharePoint, Power Automate, Power Apps and more. 👏 Weekly Tuesday call is for all community members to see Microsoft PMs, engineering and Cloud Advocates showcasing the art of possible with Microsoft 365 and Power Platform. 📅 On the 16th of December we'll have following agenda: News and updates from Microsoft Together mode group photo Fabian Williams – Copilot Studio × MCP: From Zero to Shipping a Real Event Agent Vesa Juvonen – Introduction to SharePoint Pages Agent in Microsoft 365 Copilot 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/ms-speakers-call-join 👋 See you in the call! 🎅🎄 Notice that this call is on a holiday break after 16th of December call and back on 13th of January 2026. 💡 Building something cool for Microsoft 365 or Power Platform? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/homeMicrosoft 365 & Power Platform Community call - Community demos
💡 Microsoft 365 & Power Platform Development bi-weekly community call focuses on different use cases and features within the Microsoft 365 and Power Platform - across Microsoft 365 Copilot, Copilot Studio, SharePoint, Power Apps and more. 👏 Looking to catch up on the latest news and updates, including cool community demos, this call is for you! 📅 On 11th of December we'll have following agenda: Copilot prompt of the week SharePoint Framework roadmap update from Microsoft Latest on PnPjs project Latest on CLI for Microsoft 365 Latest on Dev Proxy Latest on reusable controls for SPFx Latest on SPFx Toolkit VS Code extension Latest on PnP Search solution for enterprise search Latest on SPFx samples Picture time with the Together Mode! Aimery Thomas (Avanade) – SP Shortcuts - Quick access to SharePoint setting pages Elio Struyf (Struyf Consulting) – Bringing Intelligence to Enterprise Search with Microsoft Foundry Hugo Bernier (Takeda) – AI powered layout creation - Building AI integrated SPFx web part 📅 Download recurrent invite from https://aka.ms/community/m365-powerplat-dev-call-invite 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/m365-powerplat-dev-call-join 👋 See you in the call! 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!Microsoft 365 & Power Platform product updates call
💡Microsoft 365 & Power Platform product updates call concentrates on the different use cases and features within the Microsoft 365 and in Power Platform. Call includes topics like Microsoft 365 Copilot, Copilot Studio, Microsoft Teams, Power Platform, Microsoft Graph, Microsoft Viva, Microsoft Search, Microsoft Lists, SharePoint, Power Automate, Power Apps and more. 👏 Weekly Tuesday call is for all community members to see Microsoft PMs, engineering and Cloud Advocates showcasing the art of possible with Microsoft 365 and Power Platform. 📅 On the 9th of December we'll have following agenda: News and updates from Microsoft Together mode group photo Reid Carlberg – SharePoint Embedded Wrapped 2025: Updates from Ignite and More Paolo Pialorsi – Leveraging Microsoft 365 Copilot APIs in SPFx solutions 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/ms-speakers-call-join 📅 You can also download recurrent invite to this call from https://aka.ms/community/ms-speakers-call-invite 👋 See you in the call! 🎅🎄 Notice that this call is on a holiday break after 16th of December call and back on 13th of January 2026. 💡 Building something cool for Microsoft 365 or Power Platform? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home
SharePoint Knowledge Agent Vs Power automate AI builder
If we want to classify, summarize and extract key info from documents uploaded/edited inside a SharePoint document libraries. seems we can do this using AI builder inside power automate which get triggered when add/edit a document or using the Knowledge Agent, mainly the "Organize this library" option. can any one advice when you use each?
MS Forms suggested upgrades
Greetings, I've been using MS Forms for a while now. I love the concept and how it works but I think its a bit limiting. I strongly suggest the improvements listed below. 1) Add static information text fields to forms that are not numbered and are not for user response. 2) Have the ability to use 2 images, a separate form Header image and different Image for the background. 3) The ability to change the default text on the button from, "Start Now" to something more appropriate with the form.Streamline your contact center telephony with Teams Phone extensibility
Microsoft Teams Phone brings intelligent, cloud-based calling to Teams, streamlining operations and delivering secure, reliable voice experiences. Until recently, however, enabling enterprise calling in the contact center meant deploying separate solutions, adding administrative complexity and redundant costs. Today, we’re excited to announce the general availability of Teams Phone extensibility for a growing ecosystem of contact center solutions, including Microsoft Dynamics 365 Contact Center. This new capability allows customers to extend Teams Phone investments into the contact center, enabling customers to use a single, integrated calling solution across both unified communications (UCaaS) and contact center (CCaaS) environments. Organizations can leverage Teams Phone extensibility to: Apply existing Teams Phone licenses to enable telephony for users of Dynamics 365 Contact Center or other certified ISV contact center solutions 1 . Avoid procuring, configuring, managing, and training users on a separate phone system for contact center deployments. Leverage the broad geographic availability of Teams Phone through calling plans available in 36 countries, Operator Connect in 96 countries, and Direct Routing globally. Benefit from the extensive features of Teams Phone, including the familiar Teams management interface. With these benefits, you can now streamline your telephony and reduce the number of solutions to license and manage across your organization. Learn more about the features of Teams Phone extensibility including conversational AI integration. Unify your calling capabilities for time and cost savings Teams Phone extensibility is a significant development for customers. It reflects how Dynamics 365 Contact Center helps organizations innovate faster and reduce costs with Microsoft’s unified cloud platform, low-code tools, and built-in AI – making it easier to build, manage, and scale contact center solutions without complex infrastructure or costly custom development. Teams Phone extensibility enables organizations to unify calling and contact center experiences for both agents and customers, all within a secure, familiar Microsoft environment. A commissioned Total Economic Impact™ study conducted by Forrester Consulting found that organizations using Teams Phone extensibility with Dynamics 365 Contact Center could achieve a projected return on investment up to 345% over three years 2 . These savings stem from lower operational and service fees, streamlined administration, and greater call center efficiency. With its certification in progress, Teams Phone extensibility with Dynamics 365 Contact Center is more than an integration. It’s a shift toward unified, intelligent communication that helps businesses operate smarter and deliver better customer experiences. Download the full study to learn more. ISV partners provide additional choice and flexibility Teams Phone extensibility is also supported by contact center ISV solutions that utilize the Teams Unify integration model. With Unify, ISVs build directly on Microsoft infrastructure, using Azure Communication Services (ACS) and gaining access to Microsoft Copilot and Cognitive Services. This approach enables them to embed advanced features and intelligence, resulting in richer, more unified solutions that help organizations deliver efficient, secure, and customer-focused interactions. ISV solutions that have completed certification for Teams Phone extensibility include AudioCodes, CentrePal, ComputerTalk, Heedify, and Landis. 1 We look forward to adding additional certified contact solutions to this growing ecosystem in the months ahead. If you are a contact center developer, learn more about enabling Teams Phone calling for your CCaaS solution. Contact center ISVs that are Unify-model certified for Teams Phone extensibility include AudioCodes, CentrePal, ComputerTalk, Heedify, and Landis. Power your contact center with the calling capabilities of Teams Phone If you're already using Teams Phone and Dynamics 365 Contact Center or any of the certified ISV solutions, you can start taking advantage of Teams Phone extensibility today. Not yet using these solutions? You can set up trials for both Teams Phone and Dynamics 365 Contact Center to explore the benefits firsthand. If you're interested in trialing Teams Phone extensibility with a certified ISV contact center solution, please contact your preferred CCaaS vendor for more information. 1 While certification is not required to access the Azure Communication Services API that enables Teams Phone extensibility, we recommend selecting a contact center solution that has completed the certification process for the best experience. 2 Projected benefits for a composite customer. New Technology: The Projected Total Economic Impact™ Of Microsoft Dynamics 365 Contact Center with Teams Phone extensibility, Forrester Consulting, Casey Sirotnak, Jonathan Lipsitz, August 2025.
SPFX call gets error "interaction required" after turning on function's System Assigned Identity
I have an spfx web part that is connected an Azure Function. All was working until I turned on the System Assigned Identity for the function. Below is my configuration while it was working: Function app: contoso-fn App Service authentication enabled Unauthenticated requests get a 302 HTTP code Microsoft is the identity provider, with app registration "contoso-fn-auth" It allows token audiences from api://<id-contoso-fn-auth> and from <my-tenant>.sharepoint.com Allowed client applications include 08e18876-6177-487e-b8b5-cf950c1e598c and <id-contoso-fn-auth> CORS: https://learn.microsoft.com/en-us/answers/questions/4374948/spfx-making-call-to-azure-function-gets-error-inte and https://<my-tenant>.sharepoint.com App registration "contoso-fn-auth" (used above when setting up identity provider) Authentication > Web > Redirect URI: https://learn.microsoft.com/en-us/answers/questions/4374948/spfx-making-call-to-azure-function-gets-error-inte ID tokens issued only accounts in the tenant can access this API API permissions > contoso-fn-auth > user_impersonation ; Delegated; Status: granted for tenant Expose an API: Scopes api://<id-contoso-fn-auth>/user_impersonation The code in the SPFX to request the function is something like this: this.context.aadHttpClientFactory .getClient('<id-contoso-fn-auth') .then((client: AadHttpClient): void => { client.get(<url-to-the-fn>/api/upload)...}); In the SharePoint Admin Center, under Advanced > API Access, the user_impersonation permission is approved for contoso-fn. I then changed the Function app identity, turning on "system assigned", as I needed the function to authenticate against the Azure Blob Client, and now I'm getting the following error: interaction_required: Seamless single sign on failed for the user. This can happen if the user is unable to access on premises AD or intranet zone is not configured correctly I read something about turning on the function's system assigned identity affecting how I requests tokens using the aadHttpClientFactory, but I haven't been too successful in finding how to solve the issue (including internet search and asking several LLMs). I don't need my function to have user context (I could send that from the spfx) but I need this to work without any redirects. I would appreciate help to be able to call the function from the spfx seamlessly, while keeping the function secured with Microsoft identity. (porting from a https://learn.microsoft.com/en-us/answers/questions/4374948/spfx-making-call-to-azure-function-gets-error-inte, as requested)Getting error when trying to get user access token in SPfx solution using MSAL
Referring https://github.com/microsoft/CopilotStudioSamples/tree/main/SharePointSSOComponent and tried to implement it. Getting error when trying to get user access token using MSAL. The Error is: Unsafe attempt to initiate navigation for frame with origin 'https://XXXX.sharepoint.com' from frame with URL 'https://login.microsoftonline.com/XXXXXXXX-595d-472c-8248-0dc58f852d61/oaut…04MDZhLTc4NTFlOGEzNWJjNSIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoic2lsZW50In19'. The frame attempting navigation of the top-level window is sandboxed, but the flag of 'allow-top-navigation' or 'allow-top-navigation-by-user-activation' is not set. Issue is intermittent and usually occurs when running on local
