Our File Handler custom actions are not appearing in the OneDrive for Business / SharePoint Online context menus. The _api/v2.0/drive/apps endpoint returns an empty "value": [] array, indicating the file handler has never been registered in SharePoint's cache (while we could locate and use the actions ~2 days ago.
What We've Verified:
-
The application is online and all URLs return HTTP 200 (action URLs, icon URLs)
-
The addIns section exists and is correctly structured in the Azure AD manifest
-
The app is not hidden ("tags": [])
-
The client secret is valid
-
Admin consent has been granted for the tenant
-
Tested in incognito/private browsing — not visible _api/v2.0/drive/apps returns {"@odata.context":"...","value":[]} — empty
-
Re-consented — still empty after multiple hours
-
Attempted $forceRefresh=1 cache reset — still empty
Some questions:
-
Is there a known issue with file handler recently?
-
Are there additional requirements beyond the addIns manifest and consent for file handlers to be picked up by SharePoint?
-
Is there a way to force SharePoint to re-scan Azure AD app registrations for file handler manifests?
Our File Handler custom actions are not appearing in the OneDrive for Business / SharePoint Online context menus. The _api/v2.0/drive/apps endpoint returns an empty "value": [] array, indicating the file handler has never been registered in SharePoint's cache (while we could locate and use the actions ~2 days ago.
What We've Verified:
The application is online and all URLs return HTTP 200 (action URLs, icon URLs)
The addIns section exists and is correctly structured in the Azure AD manifest
The app is not hidden ("tags": [])
The client secret is valid
Admin consent has been granted for the tenant
Tested in incognito/private browsing — not visible _api/v2.0/drive/apps returns {"@odata.context":"...","value":[]} — empty
Re-consented — still empty after multiple hours
Attempted $forceRefresh=1 cache reset — still empty
Some questions:
Is there a known issue with file handler recently?
Are there additional requirements beyond the addIns manifest and consent for file handlers to be picked up by SharePoint?
Is there a way to force SharePoint to re-scan Azure AD app registrations for file handler manifests?