You have a Microsoft 365 tenant. You develop a custom Microsoft Office Add-in for Word. You need to sideload the add-in. You sign in to Microsoft 365 in a web browser and created a new Word…

The correct answer is B. Upload the add-in to the tenant app catalog. When Add-ins get embedded into documents using side loaded Add-ins, it is important to know that the Add-ins get embedded with the path of the shared drive. If other users are using a different path for the side loaded Add-in, the Add-in will not appear for them as the path is…

Extend Office

Question

You have a Microsoft 365 tenant. You develop a custom Microsoft Office Add-in for Word. You need to sideload the add-in. You sign in to Microsoft 365 in a web browser and created a new Word document. What should you do next?

Options

AUpload the add-in to Microsoft AppSource.
BUpload the add-in to the tenant app catalog.
CAttach a remote debugger by using Microsoft Visual Studio Code.
DSelect Upload My Add-in and verify that the add-in was installed.

How the community answered

(37 responses)

A
5% (2)
B
81% (30)
C
3% (1)
D
11% (4)

Explanation

When Add-ins get embedded into documents using side loaded Add-ins, it is important to know that the Add-ins get embedded with the path of the shared drive. If other users are using a different path for the side loaded Add-in, the Add-in will not appear for them as the path is not identical to the one used to embedded the Add-in. https://help.officeatwork.com/en/articles/299-deploying-office-add-ins-via-sideloading

Topics

#Office Add-in#sideloading#Word#tenant app catalog

Community Discussion

No community discussion yet for this question.

Full MS-600 Practice