Issue: Word Online displays 'TA field codes' with embedded 'LineBreak' as GreyBox and new line
Scenario : We are experiencing an issue in Word Online where displaying "TA field codes" that contain embedded line breaks shows them as gray boxes and also introduces unwanted extra blank lines. Steps to reproduce: Open any word document Insert TA field codes that include a LineBreak. Copy the document link from OneDrive and open the same document in a browser (preferably Chrome) using that link. Observe that Word Online displays gray boxes in the document where TA field codes with LineBreak. Below are screenshots from Word Online and Word desktop for comparison: Please note that, "TA field code" in Line 1 contains no embedded line breaks, whereas the "TA field code" in Line 2 does. 1. Desktop Word: Below screenshot is for Desktop word after 'show paragraph marks' is on. 2. Word Online : Below Screenshot without paragraph symbol : a line break character inside a hidden tag is causing a grey box issue in word online Expected behavior: Word Online shouldn't display gray boxes or extra lines, even when the TA field code contains embedded line breaks.. Current behavior: When a TA field code includes an embedded line break, Word Online shows a new, extra line and displays gray boxes. Environment: Platform : PC Desktop Host: Word Office version number: Any Operating System: Windows Browser (if using Office on the web): Chrome and MSEdge Context This issue will be directly impacted to the customers who are all using Word Online. Please let me know any other information required .. I've attached a document that explains how to manually recreate this issue. => https://github.com/user-attachments/files/20576971/Ticket_TA.newline.docx Thank you
Office.js API — Open OneDrive Files in Current Word/PPT Instance
Currently, Office.js does not provide an API to directly open a OneDrive (or SharePoint Online) file in the current Word/PPT desktop instance. For add-ins that integrate with external systems, this creates a significant limitation. Users often need to: Access Word/PPT documents stored in OneDrive/SharePoint directly from an add-in. Ensure the file opens seamlessly in the same Word/PPT session, without forcing them to manually download or open a new instance. Why this is important Improves user workflow and productivity. Essential for add-ins that sync or integrate with cloud storage and external systems. Avoids user confusion from multiple Word windows or manual file handling. Requested capability An Office.js API such as: Office.context.document.openFileFromUrl(fileUrl, options); where fileUrl is a OneDrive/SharePoint URL and options could specify whether to open in the current instance or a new one. This would align Office.js capabilities more closely with real-world workflows and reduce friction for both developers and end-users.
Feature Request: Add error/rejection support to Office.onReady() for network/dependency failures
Description Currently, when Office.js loads but one of its dependent resources (such as office_strings.js) fails to load due to network issues or blocking, the Office.onReady() promise never resolves or rejects. This leaves developers without a reliable way to detect missing dependencies. Instead of relying on timeouts or log messages, it would be very helpful if Office.onReady() provided an error callback or rejection in these scenarios. Why this matters: Helps developers handle production failures gracefully. Avoids arbitrary timeouts/workarounds to detect missing dependencies. Provides parity with modern async practices where promises resolve or reject deterministically. Enables better telemetry/analytics by explicitly knowing why initialization failed. Suggested Approach: If a required dependency fails to load, Office.onReady() should reject with an error describing the missing dependency. Alternatively, provide an event/callback (e.g., Office.onError) that developers can subscribe to. Example: Office.onReady() .then(info => { console.log("Office.js initialized:", info); }) .catch(err => { console.error("Office.js failed to initialize:", err); // custom fallback handling }); Impact: This would improve developer experience significantly and make add-ins more resilient in real-world network environments.Add viewportChanged event to Word JavaScript API
In Word add-ins, we often need to react to changes in the user's viewport (scrolling, zooming, etc.). Currently, there's no event to detect when the visible pages change. A viewportChanged event on Word.Pane or Word.Window would allow developers to optimize performance and create dynamic experiences based on what the user is viewing.Subject: Disabled GPT-5 Button and Missing Copilot in Word, Excel, PowerPoint
Hello everyone, I’m developing a complementary app/feature in Office 365/Power Automate/etc., and I’m encountering a couple of issues that I can’t resolve. Here are the details: Description of the issues: Disabled Button: The button name in my interface is disabled for no apparent reason. It doesn’t get activated even when all conditions for it to be enabled should be met. There are no error messages, and the browser console doesn’t show any relevant warnings. Missing Copilot Button (GPT-5): In my Microsoft 365 apps (Word, Excel, PowerPoint), the Copilot (GPT-5) button is not showing up. I’ve checked the settings, but it seems it’s not enabled or appearing in the interface, even though it should be available. Environment: Microsoft 365 Apps: Word, Excel, PowerPoint Platform Version: [Indicate the version of Office 365 you’re using] Development Language: [e.g., JavaScript, C#, VBA, etc.] Additional Dependencies: [If you’re using any external libraries or APIs, mention them here] What I’ve tried so far: I’ve checked the events associated with the disabled button, but it remains inactive. I checked for errors in the console, but didn’t find anything relevant. I tried clearing the cache and reloading the page, but the issue persists. I reviewed Microsoft 365 documentation regarding Copilot (GPT-5), but the button still doesn’t appear in my interface. Question: Has anyone experienced a similar issue or knows what might be causing: The button to stay disabled without any apparent reason? The Copilot (GPT-5) button to not show up in Word, Excel, and PowerPoint? Any help or suggestions would be greatly appreciated. Thank you in advance!Subject: Disabled GPT-5 Button and Missing Copilot in Word, Excel, PowerPoint
Hello, I’m having two issues with Microsoft 365: A button in my app is disabled without reason and doesn’t activate despite meeting all conditions. The Copilot (GPT-5) button is missing in Word, Excel, and PowerPoint, even though it should be there. Environment: Apps: Word, Excel, PowerPoint Platform Version: [your Office 365 version] Development Language: [e.g., JavaScript, C#, VBA] What I’ve tried: Checked button events (still inactive). Cleared cache and reloaded. Reviewed Copilot docs, but the button is still missing. Has anyone faced this or have suggestions on how to fix it? Thanks in advance!
Add resourceAppId property to oAuth2PermissionGrant
To check what permissions are granted by our clients, we use application mode and get the servicePrincipal, this works fine for the permissions of type applications. The problem lies in the delegated permissions. Currently, oAuth2PermissionGrant exposes only resourceId (servicePrincipalId which is different from tenant to tenant) and no resourceAppId. So we need to get this servicePrincipal by this resourceId to get the appId. The problem here is that we are not allowed to do this unless we have an Application.Read.All which we cannot ask or justify to our clients because it is an elevated permission.
Limitation with Static AppDomain Entries in Office Add-in Manifest
As outlined in the [Microsoft documentation](https://learn.microsoft.com/en-us/javascript/api/manifest/appdomain), trusted domains must be explicitly declared in the Office Add-in manifest using the <AppDomain> element. A trusted domain allows: - Pages, routes, or other resources in that domain to be opened directly in the root task pane on desktop Office platforms (note: this does not apply to Office on the web or dialog APIs). - Pages in that domain to make Office.js API calls from IFrames within the add-in. We are currently developing a first-party native Excel Add-in as part of a strategic partnership. However, our architecture requires support for customer-specific subdomains, such as: ``` <AppDomain>https://customer1.company.com</AppDomain> <AppDomain>https://customer2.company.com</AppDomain> <AppDomain>https://customer3.company.com</AppDomain> <AppDomain>https://customer4.company.com</AppDomain> ``` This list is dynamically growing, making it infeasible to maintain a static list of subdomains in the manifest. Each manifest update would require re-submission through AppSource, creating significant operational overhead and slowing down delivery. Because of this limitation, we’re forced to distribute customer-specific manifests and rely on M365 tenant admins to install the add-in manually—introducing friction and reducing discoverability for users. We propose enabling wildcard support for <AppDomain> entries in the manifest, e.g.: ``` <AppDomain>https://*.company.com</AppDomain> ``` This would allow all subdomains under company.com to be trusted without requiring individual enumeration, simplifying deployment and scaling while preserving security. This limitation has been highlighted and highly upvoted by the developer community in the following feature requests: - https://techcommunity.microsoft.com/idea/microsoft365developerplatform/add-in-manifest-allow-wildcards-for-app-domains/4162573 - https://techcommunity.microsoft.com/idea/microsoft365developerplatform/support-wildcards-for-appdomains-in-office-add-in-manifests-to-support-sub-domai/2312326Word JS API - Add date picker, repeating section and combo box content controls
Currently only rich text content controls and check box content controls are available through the Word API https://learn.microsoft.com/en-us/javascript/api/word/word.contentcontrol?view=word-js-preview#word-word-contentcontrol-getcontentcontrols-member(1) Could you add support for date picker, repeating section and combo box content controls. The best would be if all content control types are supported. But for the company where i work at the above 3 are needed.
