This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 14.000000000000002%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I am using Visual Studio and Azure to host a web app.
The web app is a Word taskpane.
When i run the taskpane in test mode in Visual Studio it works fine but when i publish it and load it via Azure the taskpane only opens to Internet Explora.
The taskpane remains open while Internet Explora pops up in a window with the contents.
I have included:
ffice.initialize = function () {
if (!Office.context.requirements.isSetSupported('WordApi', '1.1')) {
console.log("Sorry, this add-in only works with newer versions of Word.");
}
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 86%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDC%3C/text%3E%3C/svg%3E)
Hi @Mandz , can you please provide more information about the specific version of the browser you are using, and if this is Word on Windows, or Mac? Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 16%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Windows configuration
word taskpane
windows 11 installed
Ok. How are you loading the add-in to Word on Windows? Once you deploy to Azure, you would typically use either central deployment, or AppSource. You can still sideload as well. Whichever load approach you use you must use an updated manifest.xml file that is updated for the Azure Urls of your web project. When you first create the Visual Studio project, the manifest will reference https://localhost/... Did you update the manifest to use the web app locations on Azure?
Thanks,
David