You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: microsoft-365/admin/manage/deploy-addins-for-gcch.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,13 +40,14 @@ Centralized deployment for Office Add-ins can be managed at an administrative le
40
40
12. On the <b>Configure add-in</b> page, choose the users you want to have access to the add-in, then select <b>Deploy</b>.
41
41
13. If the above steps fail to deploy the Add-in, it's possible your Tenant is blocking the store. If this is the case, please continue.
42
42
14. Paste the URL built out from step 4 above into a browser. This is the raw xml.
43
-
15. Copy the xml and paste into notepad.
44
-
16. Name the file <b>Manifest.xml</b>.
45
-
17. Instead of using the URL option, choose <b>I have the manifest file (.xml) on this device</b>.
46
-
18. Click on <b>Choose File</b>.
47
-
19. Browse to your <b>Manifest.xml</b> file and select it.
48
-
20. Select <b>Upload</b>.
49
-
21. On the <b>Configure add-in</b> page, choose the users you want to have access to the add-in, then select <b>Deploy</b>.
43
+
15. <b>Righ-Click</b> on the page.
44
+
16. Select <b>Save As</b> and save as an <b>.xml</b>.
45
+
17. Name the file <b>Manifest.xml</b> or another descriptive name.
46
+
18. Instead of using the URL option, choose <b>I have the manifest file (.xml) on this device</b>.
47
+
19. Click on <b>Choose File</b>.
48
+
20. Browse to your <b>Manifest.xml</b> file and select it.
49
+
21. Select <b>Upload</b>.
50
+
22. On the <b>Configure add-in</b> page, choose the users you want to have access to the add-in, then select <b>Deploy</b>.
50
51
51
52
> [!IMPORTANT]
52
53
> After selecting <b>Deploy</b>, if there's an error concerning Admin Consent, the Add-in isn't GccH compatible and the Developer of the Add-in should be contacted to allow their Add-in to be GccH compliant.
0 commit comments