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
Prevent Automatically Opening the File Explorer on the Upload Tab (filepicker)
I am working on an application customizer that will inject custom UI into the File Picker's Upload tab. Because of this, I want to prevent the file explorer from automatically opening when the user clicks on the Upload tab. I’ve tried several methods to achieve this by manipulating the DOM through my custom code in the application customizer. I even tried removing the "file" input element from my custom code. However, the file explorer still opens automatically when the user clicks on the Upload tab. Is there any way to prevent this?
Newly submitted items are not displayed when SPFx Field Customizer
When applying the SPFx Field Customizer, the list will be displayed in the old UI. When I post an item to the old UI list, the latest item posted is shown in the list view, but it does not immediately appear on the screen where it is pasted as a web part on the page. Steps: Prepare a list with SPFx's Field Customizer applied Display the target list on the page Display the page and the list in separate tabs Post an item to the target list The item does not appear on the page where the list web part is placed Reloading (F5) on the page sometimes shows or does not show the latest item
Curious: Are SPFx Extensions Supported in OneDrive?
Hi everyone, 👋 I'm fairly new to the SharePoint Framework (SPFx) world and have been exploring its possibilities. It's been an exciting journey so far, but I’ve hit a bit of a question that I couldn't find a clear answer to. Does anyone know if SPFx extensions are supported in OneDrive? I understand they work great in SharePoint, but I’m wondering if we can extend the same functionality to OneDrive. If not, does anyone have insights into whether there’s a chance that Microsoft might bring SPFx extensions to OneDrive in the future? I’d love to hear your thoughts or any advice you have to share! Thanks for taking the time to help. 😊 Cheers, Sachin
Form Customization Permissions?
1. I wrote a SharePoint form customization using SPFx ( TypeScript / React ). 2. I have a large pool of external users and each month I will send emails to a portion of those users. 3. The email will contain a link back to a page on my SharePoint site. 4. The page on the site will contain one or more links to list items that require the user to edit and save. 5. When the user clicks on one of those links, the corresponding list item will be displayed using my form customization. 6. The user will edit the information, save the form, and be directed back to the site page with the links to the list items. Everything works fine up to (and including) #4. However, when the user clicks on one of those links, only a blank page appears and using F12 I see the following: ----------------------------------------------------------------------------------------------------------------- Refused to execute script from 'https://<tenant>/sites/appcatalog/_layouts/15/AccessDenied....' because it's MIME type ('text/html') is not executable, and string MIME type checking is enabled ----------------------------------------------------------------------------------------------------------------- The users are all included in the "members" group of the site and should have edit permissions. However, this error message seems as though there is some permission missing from the actual form customization application that I deployed to the app catalog and then enabled on this specific site. Internal users do not experience this issue, only external users. Are there permissions I need to configure on a form customization application?
