But there seems also to be no way to add an allowed origin for cross-domain requests for these types of API. Of course Microsoft won't allow any foreign domain to directly consume their resources, security comes first in the cloud. Trying to make the call client-side in the browser reveals the first major problem: Cross-Origin Resource Sharing (CORS) restrictions. Great, so why not directly use this API in your old world on-premises application? Unfortunately it's not that easy, at least. The most obvious request calls the following endpoint: Request to returns all apps from the App LauncherĪs seen in the above image, all relevant app information is returned from this API. Wouldn't it be nice if the legacy applications would have the same app launcher integrated into their UI? Of course it would be! But nice doesn't mean it's easy to do.īy trying to reverse engineer the Office 365 pages, there are some APIs used to gather the related information for the apps displayed in the app launcher. So what is one of the most recognizible parts of Office 365? Of course the App Launcher, your quick-start to all Office 365 applications: The Office 365 App Launcher is available across all Office 365 services, like SharePoint, OneDrive, Word, Excel, Planner, Power BI. In this specific case, the term new world refers to Office 365, while the old world could be any other internal system not yet ready to move to the cloud. To support user adoption, some items from the new world should be introduced to the old world. While some business applications are quickly moved to the cloud, others remain on-premises for the time being.
0 kommentar(er)
