Ability to Assign Custom Properties or Unique IDs to Individual Cells
Summary I'd like to request support for assigning custom metadata — such as unique IDs or arbitrary key-value pairs — directly to individual cells in Excel using the Office.js API. Why This Matters Currently, developers must rely on workarounds like named ranges, hidden metadata sheets, or cell notes to simulate per-cell identifiers. These approaches are either limited, fragile, or not scalable for large applications. Native support for cell-level metadata would unlock powerful use cases: Dynamic form builders Cell-level validation engines Workflow tracking Data lineage and audit trails Integration with external systems via stable cell references Proposed API Concept range.customProperties.add("id", "cell_001"); const id = range.customProperties.getItem("id").value; Or even: range.metadata = { id: "cell_001", status: "approved", validator: "admin" }; Benefits Eliminates reliance on fragile naming conventions Enables scalable, structured metadata management Improves developer experience and app robustness Alternatives Considered Named ranges: limited and global scope Notes/comments: visible to users, not structured Hidden metadata sheets: hard to maintain Custom XML parts: complex and not cell-specific Request Please consider adding support for cell-level metadata or custom properties in a future version of Office.js. Even a lightweight key-value store per cell would be a game-changer.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.
Config Azure application proxy using the graph API
I added https://stackoverflow.com/questions/75145084/config-azure-application-proxy-using-the-graph-api explaining the issue. It would be great to release endpoints that I could use to https://learn.microsoft.com/en-us/graph/application-proxy-configure-api?tabs=http. The list of the endpoints: PATCH https://graph.microsoft.com/beta/applications/bf21f7e9-9d25-4da2-82ab-7fdd85049f83 Content-type: application/json { "onPremisesPublishing": { "externalAuthenticationType": "aadPreAuthentication", "internalUrl": "https://contosoiwaapp.com", "externalUrl": "https://contosoiwaapp-contoso.msappproxy.net", "isHttpOnlyCookieEnabled": true, "isOnPremPublishingEnabled": true, "isPersistentCookieEnabled": true, "isSecureCookieEnabled": true, "isStateSessionEnabled": true, "isTranslateHostHeaderEnabled": true, "isTranslateLinksInBodyEnabled": true } } GET https://graph.microsoft.com/beta/onPremisesPublishingProfiles/applicationProxy/connectors POST https://graph.microsoft.com/beta/onPremisesPublishingProfiles/applicationProxy/connectorGroups Content-type: application/json { "name": "IWA Demo Connector Group" } PUT https://graph.microsoft.com/beta/applications/bf21f7e9-9d25-4da2-82ab-7fdd85049f83/connectorGroup/$ref Content-type: application/json { "@odata.id":"https://graph.microsoft.com/onPremisesPublishingProfiles/applicationproxy/connectorGroups/3e6f4c35-a04b-4d03-b98a-66fff89b72e6" } PATCH https://graph.microsoft.com/beta/applications/bf21f7e9-9d25-4da2-82ab-7fdd85049f83 Content-type: appplication/json { "onPremisesPublishing": { "singleSignOnSettings": { "kerberosSignOnSettings": { "kerberosServicePrincipalName": "HTTP/iwademo.contoso.com", "kerberosSignOnMappingAttributeType": "userPrincipalName" }, "singleSignOnMode": "onPremisesKerberos" } } } GET https://graph.microsoft.com/beta/servicePrincipals/a8cac399-cde5-4516-a674-819503c61313/appRoles POST https://graph.microsoft.com/beta/servicePrincipals/b00c693f-9658-4c06-bd1b-c402c4653dea/appRoleAssignments Content-type: appRoleAssignments/json { "principalId": "4628e7df-dff3-407c-a08f-75f08c0806dc", "principalType": "User", "appRoleId":"18d14569-c3bd-439b-9a66-3a2aee01d14f", "resourceId":"a8cac399-cde5-4516-a674-819503c61313" }
Support for Submenus in Office JS Add-in Custom Menus
Dear Microsoft 365 Developer Team, I would like to submit a feature request regarding custom menus in Word JavaScript Add-ins. Currently, when defining custom menus for the ribbon via the manifest.xml, it is possible to create a root-level menu control with a list of menu items. However, submenus (nested menus) are not supported. This limits the ability to create well-structured and user-friendly menus, especially when dealing with more complex add-ins that require logical grouping of actions. Use Case Example: Imagine an add-in that handles document templates, formatting options, and insertion of custom content. It would be much more intuitive to organize these into hierarchical menus like: My Add-in Menu | |---Templates | |---Contract Template | |---NDA Template |---Formatting | |---Apply Header | |---Apply Footer |---Insert |---Clause |---Placeholder Currently, to achieve something like this, we either have to create long flat menus, which are less user-friendly and harder to navigate, or define multiple root-level menu controls as a workaround. However, having too many root-level menus clutters the ribbon and makes the overall user experience confusing and less efficient. Feature Request: Please consider adding support for nested menu structures (submenus) in Office Add-in command definitions. This would: Greatly improve user experience for complex add-ins. Allow better organization of actions and commands. Align the Add-in UX closer to the native ribbon and menu experiences in Office apps. Possible Implementation Suggestions: Extend the Menu control to allow nested Menu or MenuItem elements. Allow referencing predefined menus to enable reuse and modularity. Related Documentation: https://learn.microsoft.com/en-us/office/dev/add-ins/reference/manifest/customtab?view=word-js-preview https://learn.microsoft.com/en-us/office/dev/add-ins/design/add-in-commands https://learn.microsoft.com/en-us/javascript/api/manifest/control-menu?view=common-js-preview Thank you for considering this enhancement. It would be a huge step forward for creating more powerful and user-friendly Office Add-ins! Best regards, Ingo
Identify multiple embedded instance of the same add-in in a file as one
Summary By default, when a file is opened in Excel with a JS add-in installed and then saved, the JS add-in is automatically embedded in the file. In the current design all embedded add-ins will be attempted to load when the file is opened even if the embedded add-ins are the same. As a result, when these files are shared with other users who already have the same JS add-in installed with a different version or deployment method, Excel displays two instances of the same add-in in the tabs, or occasionally shows an error in the task pane if the version it is embedded is an older one. We first became aware of this issue when a user reported seeing our JS add-in appear twice in the ribbon, which led to confusion. Upon inspecting the affected file’s XML web extensions, we identified two versions of the same add-in embedded: one deployed via OMEX and another via exCatalog. After further investigation and filing a ticket with Microsoft Support, it was confirmed that this behavior is by design under the current implementation. Why This Matters While we understand that this behavior is expected by design, it remains problematic for users—it can cause confusion and potential issues with custom functions or with the add-in itself. Also, it is not clear for As of the moment there are no easy workaround for users to remove the duplicate/additional instance of the same JS add-in embedded in the file, this will also need to be done for every file that is suffering from this issue (has multiple instance of the same add-in embedded in the file w/ different version/deployment method). Proposed Change/s Update current design to be able to identify if the embedded adds-in is the same through checking and comparing a unique id so even if they have different deployment/version tags it will not be loaded/attempted to be loaded in the task pane. Alternatives Considered Provide an option in Officejs API to prevent embedding/referencing add-in in a file Benefits Prevents users from seeing the same add-in appear twice in the file Eliminate propagating errors in the task pane from trying to render the same add-in with the old version tag [Alternative considered] Allow users/dev to be able to control which add-in gets embedded in the file
Outlook 365 for Mobile app - Compose window support for Office JS add-ins
We are exploring the new Office JS add-ons model for Outlook for mobile apps and wanted to integrate our product with iOS/Android apps. While exploring the new Office JS model, we didn't see any way to integrate the product with compose window. Task-pane or commandBar way of integration is missing for compose window. Compose window task-pane or commandBar integration is common use case among iOS/Android users. While composing emails, the following use cases are common in industry: Users want to insert documents or attach emails from 3rd part repository or storage or from content management software. When user sends an email, they want to keep a copy of the email in the repository also Currently these use cases are not possible with add-in model. But it is supported in desktop version as well as web version of add-ins. Without these use cases support, users wont adapt our solutions. So this is required for more user adaptability.
Microsoft Loop: Ability to create/add diagrams in pages
Often we need to explain, discuss, agree on subjects that need to be supported by diagrams. These diagrams are often subject to changes as result of the interactions with the different stakeholders. It would be important to have the ability to add these diagrams directly in the loop workspace pages, instead of inserting images.
Unable to create Microsoft 365 developer account for Indian developers
I tried to create Microsoft 365 developer account from India, but there was no option populated to select country "India (+91)" while verifying mobile numbers. so In fact all Indian developers can't create M365 developer account right now and this has been disappointing us. Could you please make the country India (+91) available on the drop down list, while verifying mobile number. so that we can create M365 developer account. kindly treat this on high priority and assist us. Thank you in advance!Add DirSync properties to /directory/onPremisesSynchronization
We need the Microsoft Graph API to return the following properties. Can they be added to the Graph API endpoint GET "/directory/onPremisesSynchronization"? DirSyncServiceAccount DirSyncApplicationType DirSyncClientMachineName DirSyncClientVersion We currently get these properties from the Get-MsolCompanyInformation, Get-MsolDirSyncConfiguration or Get-MsolDirSyncFeatures cmdlets from MSOnline but that module is EOL and also does not work for us partners who use GDAP. In /beta/organization the property onPremisesSyncEnabled is null if it is disabled and instead we think it should return the boolean false. When it is enabled it returns boolean true.
