Skip to content

Commit 266b2c4

Browse files
author
github-actions
committed
Merge branch 'main' into live
2 parents 25fd8c0 + 9ddc599 commit 266b2c4

7 files changed

+25
-20
lines changed

docs/design/keyboard-shortcuts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ For the best user experience, we recommend that you minimize keyboard shortcut c
189189
- Avoid using established keyboard shortcuts in Excel and Word. For a list, see the following:
190190
- [Keyboard shortcuts in Excel](https://support.microsoft.com/office/1798d9d5-842a-42b8-9c99-9b7213f0040f)
191191
- [Keyboard shortcuts in Word](https://support.microsoft.com/office/95ef89dd-7142-4b50-afb2-f762f663ceb2)
192-
- When the keyboard focus is inside the add-in UI, <kbd>Ctrl</kbd>+<kbd>Spacebar</kbd> and <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F10</kbd> won't work as these are essential accessibility shortcuts.
192+
- When the keyboard focus is inside the add-in UI, <kbd>Ctrl</kbd>+<kbd>Space</kbd> and <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F10</kbd> won't work as these are essential accessibility shortcuts.
193193
- On a Windows or Mac computer, if the **Reset Office Add-ins shortcut preferences** command isn't available on the search menu, the user can manually add the command to the ribbon by customizing the ribbon through the context menu.
194194

195195
## Localize the description of a keyboard shortcut

docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Make your Office Add-in compatible with an existing COM add-in
33
description: Enable compatibility between your Office Add-in and equivalent COM add-in.
4-
ms.date: 06/18/2024
4+
ms.date: 01/30/2025
55
ms.localizationpriority: medium
66
---
77

@@ -47,14 +47,16 @@ The following example shows the portion of the manifest that specifies a COM add
4747
```
4848

4949
> [!TIP]
50-
> For information about COM add-in and XLL UDF compatibility, see [Make your custom functions compatible with XLL user-defined functions](../excel/make-custom-functions-compatible-with-xll-udf.md). Not applicable for Outlook.
50+
>
51+
> - For information about COM add-in and XLL UDF compatibility, see [Make your custom functions compatible with XLL user-defined functions](../excel/make-custom-functions-compatible-with-xll-udf.md). Not applicable for Outlook.
52+
> - If you're unable to specify the **\<EquivalentAddins\>** element in the manifest of your Outlook web add-in, you must configure Group Policy instead. This only applies to Outlook. For guidance, see [Configure the Group Policy setting for Outlook add-ins](#configure-the-group-policy-setting-for-outlook-add-ins).
5153
52-
### Configure the Group Policy setting
54+
### Configure the Group Policy setting for Outlook add-ins
5355

54-
> [!IMPORTANT]
55-
> Applies to Outlook only.
56+
For Outlook web add-ins, if you're unable to update the add-in's manifest to specify the **\<EquivalentAddins\>** element, you must identify the equivalent COM add-in in the **Deactivate Outlook web add-ins whose equivalent COM or VSTO add-in is installed** Group Policy setting instead. This setting must be configured on the user's machine. Then, classic Outlook on Windows will use the COM add-in instead of the web add-in if they're both installed.
5657

57-
To declare compatibility between your Outlook web add-in and COM add-in, identify the equivalent COM add-in in the **Deactivate Outlook web add-ins whose equivalent COM or VSTO add-in is installed** Group Policy setting. This must be configured on the user's machine. Then, classic Outlook on Windows will use the COM add-in instead of the web add-in, if they're both installed.
58+
> [!NOTE]
59+
> Configuring the Group Policy setting isn't necessary if the add-in's manifest already contains an **\<EquivalentAddins\>** section.
5860
5961
1. Download the latest [Administrative Templates tool](https://www.microsoft.com/download/details.aspx?id=49030), paying attention to the tool's **Install Instructions**.
6062
1. Open the Local Group Policy Editor (**gpedit.msc**).
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
> [!IMPORTANT]
22
>
3-
> COM and VSTO add-ins aren't supported in the [new Outlook on Windows](https://insider.office.com/blog/new-outlook-for-windows-available-to-all-office-insiders) that's currently in preview. These add-ins are still supported in the classic Outlook on Windows desktop client. To learn more, see [Develop Outlook add-ins for new Outlook on Windows](../outlook/one-outlook.md).
3+
> COM and VSTO add-ins aren't supported in the [new Outlook on Windows](https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627). These add-ins are still supported in the classic Outlook on Windows desktop client. To learn more, see [Develop Outlook add-ins for new Outlook on Windows](../outlook/one-outlook.md).

docs/outlook/debug-autolaunch.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ Configure the debugger in Visual Studio Code. Follow the steps applicable to you
119119
1. Create a new folder called **Debugging** (perhaps in your **Desktop** folder).
120120
1. Open Visual Studio Code.
121121
1. Go to **File** > **Open Folder**, navigate to the folder you just created, then choose **Select Folder**.
122-
1. On the Activity Bar, select **Run and Debug** (<kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>D<kbd>).
122+
1. On the Activity Bar, select **Run and Debug** (<kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>D</kbd>).
123123
124124
![The Run and Debug icon on the Activity Bar.](../images/vs-code-debug.png)
125125

docs/publish/government-cloud-guidance.md

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Guidance for deploying Office Add-ins on government clouds
33
description: Learn how to deploy your Office Add-in to secure, government cloud environments
44
ms.topic: best-practice
5-
ms.date: 10/10/2023
5+
ms.date: 1/28/2025
66
ms.localizationpriority: medium
77
---
88

@@ -24,22 +24,25 @@ For all government cloud (i.e. Sovereign Cloud) environments, the public Microso
2424

2525
[Centralized deployment](/microsoft-365/admin/manage/centralized-deployment-of-add-ins) of add-ins outside of the store is still supported.
2626

27-
## US Government Community Cloud (GCC)
27+
In addition to requirements applicable to all Sovereign Clouds, each Sovereign Cloud environment has its own considerations that may affect Office Add-ins targeting the environment. These requirements and recommendations are described in the following sections.
2828

29-
In addition to requirements applicable to all Sovereign Clouds, each Sovereign Cloud environment has its own considerations that may affect Office Add-ins targeting the environment. GCC is the least restrictive of the government cloud environments and some of the resources required by the add-in are available from their usual production endpoints in this environment. One such resource is the Office JavaScript API library. Solution partners can continue to reference the public Office.js resource as they do with their public production solution.
29+
### US Government Community Cloud (GCC)
3030

31-
## GCC High (GCCH), US Department of Defense (DOD), or other sovereign managed clouds
31+
GCC is the least restrictive of the government cloud environments. Solution partners are permitted to reference the public Office JavaScript API library (office.js) resource as they do with their public production solution. However, we recommend that partners reference the library from the following URL.
3232

33-
These government clouds remain internet-connected, but the set of public endpoints made available is severely restricted. One such restricted endpoint is the public endpoint for loading the Office JavaScript API library. The public CDN location for Office.js will not be accessible from within these environments. However, there will be an internal, per-cloud Microsoft Office CDN provisioned with the same resource. This means the endpoint URL to access Office.js will be different and your Office Add-in may need some level of customization to run. Given the additional restrictions, it's likely that any solution provided to customers will require hosting provider services within the environment as well, necessitating additional customizations. You'll need to determine the best way to provide your solution to customers, such that it conforms to the additional restrictions imposed on services running within the boundaries of these environments. The Office JavaScript Library CDN URLs are as follows:
33+
- **GCC**: `https://appsforoffice.gcc.cdn.office.net/appsforoffice/lib/1/hosted/office.js`
3434

35-
- **GCC High**: https://appsforoffice.gcch.cdn.office.net/appsforoffice/lib/1/hosted/office.js
36-
- **DOD**: https://appsforoffice.dod.cdn.office.net/appsforoffice/lib/1/hosted/office.js
35+
### GCC High (GCCH), US Department of Defense (DOD), or other sovereign managed clouds
3736

37+
These government clouds remain internet-connected, but the set of public endpoints made available is severely restricted. One such restricted endpoint is the public endpoint for loading the Office JavaScript API library. The public CDN location for Office.js won't be accessible from within these environments. However, there'll an internal, per-cloud Microsoft Office CDN provisioned with the same resource. This means the endpoint URL to access Office.js will be different and your Office Add-in may need some level of customization to run. Given the additional restrictions, it's likely that any solution provided to customers will require hosting provider services within the environment as well, necessitating additional customizations. You'll need to determine the best way to provide your solution to customers, such that it conforms to the additional restrictions imposed on services running within the boundaries of these environments. The Office JavaScript Library CDN URLs are as follows:
3838

39-
## Airgapped Sovereign Clouds
39+
- **GCC High**: `https://appsforoffice.gcch.cdn.office.net/appsforoffice/lib/1/hosted/office.js`
40+
- **DOD**: `https://appsforoffice.dod.cdn.office.net/appsforoffice/lib/1/hosted/office.js`
41+
42+
### Airgapped Sovereign Clouds
4043

4144
These government clouds are essentially disconnected from the public internet entirely. Any resource that would normally be accessed from public resources must instead be custom-provisioned inside these cloud environments. In the GCCH and DOD clouds mentioned previously, most (if not all) solution providers will need to provision their services and resources inside the cloud. There is an option to make firewall exceptions that allows access to public services and resources. However, this bypass is not possible in airgapped clouds. As with the GCCH and DOD clouds, there will be a Microsoft Office CDN provisioned inside each cloud environment that hosts required resources such as the Office.js library. You'll need to work closely with customer tenant administrators to determine the best way to provide your services and resources in a way that conforms to the strict access requirements for airgapped Sovereign Clouds.
4245

43-
## Office 365 operated by 21Vianet
46+
### Office 365 operated by 21Vianet
4447

4548
[!INCLUDE [Information about the China-specific CDN](../includes/21Vianet-CDN.md)]

docs/tutorials/powerpoint-tutorial-vs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -620,7 +620,7 @@ Complete the following steps to add code that navigates between the slides of a
620620

621621
![The Go to Last Slide button highlighted in the add-in.](../images/powerpoint-tutorial-go-to-last-slide.png)
622622

623-
1. In Visual Studio, stop the add-in by pressing <kbd>Shift</kbd>+<kbd>F5*</kbd> or choosing the **Stop** button. PowerPoint will automatically close when the add-in is stopped.
623+
1. In Visual Studio, stop the add-in by pressing <kbd>Shift</kbd>+<kbd>F5</kbd> or choosing the **Stop** button. PowerPoint will automatically close when the add-in is stopped.
624624

625625
![The Stop button highlighted on the Visual Studio toolbar.](../images/powerpoint-tutorial-stop.png)
626626

docs/word/create-better-add-ins-for-word-with-office-open-xml.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -327,7 +327,7 @@ To turn off RSID attributes in Word for documents you create going forward, do t
327327
To remove RSID tags from an existing document, try the following shortcut with the document open in Office Open XML.
328328

329329
1. With your insertion point in the main body of the document, press <kbd>Ctrl</kbd>+<kbd>Home</kbd> to go to the top of the document.
330-
1. On the keyboard, press <kbd>Spacebar</kbd>, <kbd>Delete</kbd>, <kbd>Spacebar</kbd>. Then, save the document.
330+
1. On the keyboard, press <kbd>Space</kbd>, <kbd>Delete</kbd>, <kbd>Space</kbd>. Then, save the document.
331331

332332
After removing the majority of the markup from this package, you're left with the minimal markup that needs to be inserted for the sample, as shown in the preceding section.
333333

0 commit comments

Comments
 (0)