Skip to content

Commit a4352e4

Browse files
Merge pull request #302586 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents c0cbd00 + 227c6f6 commit a4352e4

File tree

4 files changed

+20
-16
lines changed

4 files changed

+20
-16
lines changed

articles/azure-resource-manager/management/azure-services-resource-providers.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -236,14 +236,6 @@ The resource providers for management services are:
236236
| Microsoft.SoftwarePlan | License |
237237
| Microsoft.Solutions | [Azure Managed Applications](../managed-applications/index.yml) |
238238

239-
## Media resource providers
240-
241-
The resource providers for media services are:
242-
243-
| Resource provider namespace | Azure service |
244-
| --------------------------- | ------------- |
245-
| Microsoft.Media | [Media Services](/azure/media-services/) |
246-
247239
## Migration resource providers
248240

249241
The resource providers for migration services are:

articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/interactive/messages-quickstart-interactive-messages-java.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ InteractiveMessage interactiveMessage = new InteractiveMessage(
102102
interactiveMessage.setFooter(new TextMessageContent("Logistic Ltd"));
103103
interactiveMessage.setHeader(new TextMessageContent("Shipping Options"));
104104

105-
InteractiveNotificationContent interactiveMessageContent new InteractiveNotificationContent("<CHANNEL_ID>", recipients, interactiveMessage);
105+
InteractiveNotificationContent interactiveMessageContent = new InteractiveNotificationContent("<CHANNEL_ID>", recipients, interactiveMessage);
106106

107107
// Send an interactive message
108108
SendMessageResult textMessageResult = notificationClient.send(interactiveMessageContent);
@@ -134,7 +134,7 @@ buttonActions.add(new ButtonContent("yes", "Yes"));
134134
ButtonSetContent buttonSet = new ButtonSetContent(buttonActions);
135135
InteractiveMessage interactiveMessage = new InteractiveMessage(new TextMessageContent("Do you want to proceed?"), new WhatsAppButtonActionBindings(buttonSet));
136136

137-
InteractiveNotificationContent interactiveMessageContent new InteractiveNotificationContent("<CHANNEL_ID>", recipients, interactiveMessage);
137+
InteractiveNotificationContent interactiveMessageContent = new InteractiveNotificationContent("<CHANNEL_ID>", recipients, interactiveMessage);
138138

139139
// Send an interactive message
140140
SendMessageResult textMessageResult = notificationClient.send(interactiveMessageContent);
@@ -159,12 +159,12 @@ The Messages SDK enables Contoso to send interactive WhatsApp messages, when ini
159159
In this example, the business sends a click to a link message to the user.
160160

161161
```java
162-
LinkContent urlAction = new LinkContent("Click here to find out", "https://wallpapercave.com/wp/wp2163723.jpg");
162+
LinkContent urlAction = new LinkContent("Find out more", "https://wallpapercave.com/wp/wp2163723.jpg");
163163
InteractiveMessage interactiveMessage = new InteractiveMessage(
164164
new TextMessageContent("The best Guardian of Galaxy"), new WhatsAppUrlActionBindings(urlAction));
165165
interactiveMessage.setFooter(new TextMessageContent("Intergalactic New Ltd"));
166166

167-
InteractiveNotificationContent interactiveMessageContent new InteractiveNotificationContent("<CHANNEL_ID>", recipients, interactiveMessage);
167+
InteractiveNotificationContent interactiveMessageContent = new InteractiveNotificationContent("<CHANNEL_ID>", recipients, interactiveMessage);
168168

169169
// Send an interactive message
170170
SendMessageResult textMessageResult = notificationClient.send(interactiveMessageContent);

articles/storage/blobs/blob-inventory.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -434,6 +434,16 @@ If a container or directory is deleted with soft-delete enabled, then the contai
434434

435435
Only blobs that are explicitly deleted appear in reports. Therefore, to obtain a complete listing of all soft-deleted blobs (directory and all child blobs), workloads should delete each blob in a directory before deleting the directory itself.
436436

437+
### Handling duplicates in Blob Inventory
438+
439+
Blob Inventory operates on a distributed system, which means that in rare cases, duplicate blob entries might appear in your reports.
440+
441+
If when post processing your inventory report, your use case requires unique blob entries, you can use the `Name` field to identify and return only the unique blobs.
442+
443+
444+
If your report includes blob versions, use both the `Name` and `Version ID` fields together to identify and return only the unique blobs and versions.
445+
446+
437447
## Next steps
438448

439449
- [Enable Azure Storage blob inventory reports](blob-inventory-how-to.md)

articles/update-manager/security-awareness-ubuntu-support.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,21 +17,23 @@ ms.date: 02/26/2025
1717

1818
This article provides the details on security vulnerabilities and Ubuntu Pro support in Azure Update Manager.
1919

20-
If you are using an Ubuntu 18.04 LTS image, you should take necessary steps against security vulnerabilities as the operating system reached the [end of its standard support](https://ubuntu.com/18-04/azure) in May 2023. As Canonical has stopped publishing new security or critical updates after May 2023, the risk of systems and data to potential security threats is high. Without software updates, you may experience performance issues or compatibility issues whenever a new hardware or software is released.
20+
Standard Ubuntu Long-Term Support (LTS) provides security updates for packages in the `Main` repository. However, it does not include security patching from Canonical for the thousands of packages in the `Universe` repository. This can expose systems to security threats even on a fully patched, supported LTS version.
2121

22-
You can either upgrade to [Ubuntu Pro](https://ubuntu.com/azure/pro) or migrate to a newer version of LTS to avoid any future disruption to the patching mechanisms. When you [upgrade to Ubuntu Pro](https://ubuntu.com/blog/enhancing-the-ubuntu-experience-on-azure-introducing-ubuntu-pro-updates-awareness), you can avoid any security or performance issues.
22+
For systems where the operating system has reached the [end of its standard support](https://ubuntu.com/about/release-cycle), such as Ubuntu 20.04 LTS, the risk is higher as security updates are no longer provided for the `Main` repository either.
23+
24+
To address potential patching disruptions, you can either **migrate to a newer version of LTS** or **enable Ubuntu Pro**. Migrating to a newer LTS version restores standard support for the `Main` repository. Enabling Ubuntu Pro provides [Expanded Security Maintenance (ESM)](https://ubuntu.com/security/esm), which delivers patches for the `Universe` repository on all LTS versions (`esm-apps`) and extends patching for the `Main` repository on systems that are past their standard support window (`esm-infra`).
2325

2426

2527
## Ubuntu Pro on Azure Update Manager
2628

27-
Azure Update Manager assesses both Azure and Arc-enabled VMs to indicate any action. AUM helps to identify Ubuntu instances that don't have the available security updates and allows an upgrade to Ubuntu Pro from the Azure portal. For example, an Ubuntu server 18.04 LTS instance on Azure Update Manager has information about upgrading to Ubuntu Pro.
29+
Azure Update Manager assesses both Azure and Arc-enabled VMs to identify available security updates. It will highlight when an Ubuntu VM has vulnerabilities that can be patched by enabling Ubuntu Pro. This applies to vulnerabilities in the `Universe` repository for any LTS version, and to systems past their standard support period. For example, an Ubuntu Server 18.04 LTS instance on Azure Update Manager has information about upgrading to Ubuntu Pro.
2830

2931
:::image type="content" source="./media/security-awareness-ubuntu-support/ubuntu-pro-subscription-inline.png" alt-text="Screenshot of recommendation to subscribe to Ubuntu Pro in Azure Update Manager." lightbox="./media/security-awareness-ubuntu-support/ubuntu-pro-subscription-expanded.png":::
3032

3133
You can continue to use the Azure Update Manager [capabilities](updates-maintenance-schedules.md) to remain secure after migrating to a supported model from Canonical.
3234

3335
> [!NOTE]
34-
> - [Ubuntu Pro](https://ubuntu.com/azure/pro) will provide the support on 18.04 LTS from Canonical until 2028 through Expanded Security Maintenance (ESM). You can also [upgrade to Ubuntu Pro from Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/canonical.0001-com-ubuntu-pro-bionic?tab=Overview) as well.
36+
> For detailed information on Ubuntu LTS release cycles, end-of-support dates, and official upgrade paths, see the [Canonical Ubuntu LTS end of standard support guidance](/azure/virtual-machines/workloads/canonical/ubuntu-els-guidance).
3537
> - Ubuntu offers 20.04 LTS and 22.04 LTS as a migration from 18.04 LTS. [Learn more](https://ubuntu.com/18-04/azure).
3638
3739

0 commit comments

Comments
 (0)