How to deploy Outlook Web Addin Manifest on IIS so that users can add via their My add-ins > Custom...
I have created an Outlook Web Add-in that runs great and all users can add it to their My add-ins > Custom add-ins from the Store icon on Outlook 365 when choosing to Add from file. However, when trying to load the same manifest from Add from URL Outlook is showing the following dialog.
I did download the validate-office-addin using npm. Here is the Validation "Passed" result:
All users who are trying to add the add-in from the URL have access to the web server and can browse the manifest file and see the XML Definition directly from a browser, such as Chrome.
Are there any steps that I am missing that should allow this to be available for adding the add-in from a URL?
Thanks
outlook-web-addins
asked Nov 20 at 16:33
JDev
184
add a comment |
I have created an Outlook Web Add-in that runs great and all users can add it to their My add-ins > Custom add-ins from the Store icon on Outlook 365 when choosing to Add from file. However, when trying to load the same manifest from Add from URL Outlook is showing the following dialog.
I did download the validate-office-addin using npm. Here is the Validation "Passed" result:
All users who are trying to add the add-in from the URL have access to the web server and can browse the manifest file and see the XML Definition directly from a browser, such as Chrome.
Are there any steps that I am missing that should allow this to be available for adding the add-in from a URL?
Thanks
outlook-web-addins
asked Nov 20 at 16:33
JDev
184
The Exchange Server(s) has to be able to browse to the URL. Please check this.
– Brian Clink
Nov 20 at 17:43
Also in our Exchange 2016 on-prem environment, the Exchange Server is making the request to the manifest URL using an empty user-agent string, in case you have some module denying requests based on user-agent string.
– Brian Clink
Nov 20 at 18:12
Did you provide a URL that is only accessible from inside the company, and the the mailbox is in O365? If so, this won't work with the URL option, because the Exchange Server where the mailbox is located will try to retrieve the manifest via the URL. If the mailbox is on-prem then this may work, but not in general. The next problem is whether the user can access where the office add-in is running from (e.g. the URLs defined within the manifest), after the manifest is installed.
– Brian Clink
Nov 20 at 19:26
add a comment |
I have created an Outlook Web Add-in that runs great and all users can add it to their My add-ins > Custom add-ins from the Store icon on Outlook 365 when choosing to Add from file. However, when trying to load the same manifest from Add from URL Outlook is showing the following dialog.
I did download the validate-office-addin using npm. Here is the Validation "Passed" result:
All users who are trying to add the add-in from the URL have access to the web server and can browse the manifest file and see the XML Definition directly from a browser, such as Chrome.
Are there any steps that I am missing that should allow this to be available for adding the add-in from a URL?
Thanks
outlook-web-addins
asked Nov 20 at 16:33
JDev
184
I have created an Outlook Web Add-in that runs great and all users can add it to their My add-ins > Custom add-ins from the Store icon on Outlook 365 when choosing to Add from file. However, when trying to load the same manifest from Add from URL Outlook is showing the following dialog.
I did download the validate-office-addin using npm. Here is the Validation "Passed" result:
All users who are trying to add the add-in from the URL have access to the web server and can browse the manifest file and see the XML Definition directly from a browser, such as Chrome.
Are there any steps that I am missing that should allow this to be available for adding the add-in from a URL?
Thanks
outlook-web-addins
outlook-web-addins
asked Nov 20 at 16:33
JDev
184
asked Nov 20 at 16:33
JDev
184
asked Nov 20 at 16:33
JDev
184
asked Nov 20 at 16:33
JDev
184
asked Nov 20 at 16:33
JDev
184
184
The Exchange Server(s) has to be able to browse to the URL. Please check this.
– Brian Clink
Nov 20 at 17:43
Also in our Exchange 2016 on-prem environment, the Exchange Server is making the request to the manifest URL using an empty user-agent string, in case you have some module denying requests based on user-agent string.
– Brian Clink
Nov 20 at 18:12
Did you provide a URL that is only accessible from inside the company, and the the mailbox is in O365? If so, this won't work with the URL option, because the Exchange Server where the mailbox is located will try to retrieve the manifest via the URL. If the mailbox is on-prem then this may work, but not in general. The next problem is whether the user can access where the office add-in is running from (e.g. the URLs defined within the manifest), after the manifest is installed.
– Brian Clink
Nov 20 at 19:26
add a comment |
The Exchange Server(s) has to be able to browse to the URL. Please check this.
– Brian Clink
Nov 20 at 17:43
Also in our Exchange 2016 on-prem environment, the Exchange Server is making the request to the manifest URL using an empty user-agent string, in case you have some module denying requests based on user-agent string.
– Brian Clink
Nov 20 at 18:12
Did you provide a URL that is only accessible from inside the company, and the the mailbox is in O365? If so, this won't work with the URL option, because the Exchange Server where the mailbox is located will try to retrieve the manifest via the URL. If the mailbox is on-prem then this may work, but not in general. The next problem is whether the user can access where the office add-in is running from (e.g. the URLs defined within the manifest), after the manifest is installed.
– Brian Clink
Nov 20 at 19:26
The Exchange Server(s) has to be able to browse to the URL. Please check this.
– Brian Clink
Nov 20 at 17:43
The Exchange Server(s) has to be able to browse to the URL. Please check this.
– Brian Clink
Nov 20 at 17:43
Also in our Exchange 2016 on-prem environment, the Exchange Server is making the request to the manifest URL using an empty user-agent string, in case you have some module denying requests based on user-agent string.
– Brian Clink
Nov 20 at 18:12
Also in our Exchange 2016 on-prem environment, the Exchange Server is making the request to the manifest URL using an empty user-agent string, in case you have some module denying requests based on user-agent string.
– Brian Clink
Nov 20 at 18:12
Did you provide a URL that is only accessible from inside the company, and the the mailbox is in O365? If so, this won't work with the URL option, because the Exchange Server where the mailbox is located will try to retrieve the manifest via the URL. If the mailbox is on-prem then this may work, but not in general. The next problem is whether the user can access where the office add-in is running from (e.g. the URLs defined within the manifest), after the manifest is installed.
– Brian Clink
Nov 20 at 19:26
Did you provide a URL that is only accessible from inside the company, and the the mailbox is in O365? If so, this won't work with the URL option, because the Exchange Server where the mailbox is located will try to retrieve the manifest via the URL. If the mailbox is on-prem then this may work, but not in general. The next problem is whether the user can access where the office add-in is running from (e.g. the URLs defined within the manifest), after the manifest is installed.
– Brian Clink
Nov 20 at 19:26
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397477%2fhow-to-deploy-outlook-web-addin-manifest-on-iis-so-that-users-can-add-via-their%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397477%2fhow-to-deploy-outlook-web-addin-manifest-on-iis-so-that-users-can-add-via-their%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The Exchange Server(s) has to be able to browse to the URL. Please check this.
– Brian Clink
Nov 20 at 17:43
Also in our Exchange 2016 on-prem environment, the Exchange Server is making the request to the manifest URL using an empty user-agent string, in case you have some module denying requests based on user-agent string.
– Brian Clink
Nov 20 at 18:12
Did you provide a URL that is only accessible from inside the company, and the the mailbox is in O365? If so, this won't work with the URL option, because the Exchange Server where the mailbox is located will try to retrieve the manifest via the URL. If the mailbox is on-prem then this may work, but not in general. The next problem is whether the user can access where the office add-in is running from (e.g. the URLs defined within the manifest), after the manifest is installed.
– Brian Clink
Nov 20 at 19:26