Skip to content

Commit 5b1ea14

Browse files
asudbringasudbring
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nat-bicep
2 parents a8d5304 + 44ebf28 commit 5b1ea14

File tree

8 files changed

+187
-9
lines changed

8 files changed

+187
-9
lines changed

‎articles/healthcare-apis/fhir/fhir-faq.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: FAQ about FHIR service in Azure Health Data Services
33
description: Get answers to frequently asked questions about FHIR service, such as the storage location of data behind FHIR APIs and version support.
44
services: healthcare-apis
@@ -53,6 +53,10 @@ Azure API for FHIR was our initial generally available product and is being reti
5353
- [Incremental Import](configure-import-data.md)
5454
- [Autoscaling](fhir-service-autoscale.md) enabled by default
5555

56+
By default each Azure Health Data Services, FHIR instance is limited to storage capacity of 4TB.
57+
To provision a FHIR instance with storage capacity beyond 4TB, create support request with Issue type 'Service and Subscription limit (quotas)'.
58+
> [!NOTE]
59+
> Due to issue in billing metrics for storage. Customers opting for more than 4TB storage capacity will not be billed for storage till the issue is addressed.
5660
5761
### What's the difference between the FHIR service in Azure Health Data Services and the open-source FHIR server?
5862

‎articles/healthcare-apis/fhir/fhir-features-supported.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,8 +65,9 @@ FHIR service uses [Microsoft Entra ID](https://azure.microsoft.com/services/acti
6565
## Service limits
6666

6767
* **Bundle size** - Each bundle is limited to 500 items.
68+
* **Subscription Limit** - By default, each subscription is limited to a maximum of 10 FHIR services. The limit can be used in one or many workspaces.
69+
* **Storage size** - By default each FHIR instance is limited to storage capacity of 4TB. To provision a FHIR instance with storage capacity beyond 4TB, create support request with Issue type 'Service and Subscription limit (quotas)'.
6870

69-
* **Subscription Limit** - By default, each subscription is limited to a maximum of 10 FHIR services. The limit can be used in one or many workspaces.
7071

7172
## Next steps
7273

‎articles/healthcare-apis/release-notes.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,15 @@ Azure Health Data Services is a set of managed API services based on open standa
2020

2121
This article provides details about the features and enhancements made to Azure Health Data Services, including the different services (FHIR service, DICOM service, and MedTech service) that seamlessly work with one another.
2222

23+
## January 2024
24+
25+
### FHIR Service
26+
**Storage size support in FHIR service beyond 4TB**
27+
28+
By default each FHIR instance is limited to storage capacity of 4TB. To provision a FHIR instance with storage capacity beyond 4TB, create support request with Issue type 'Service and Subscription limit (quotas)'.
29+
> [!NOTE]
30+
> Due to issue in billing metrics for storage. Customers opting for more than 4TB storage capacity will not be billed for storage till the issue is addressed.
31+
2332
## December 2023
2433

2534
### Azure Health Data Services

‎articles/postgresql/flexible-server/how-to-server-logs-cli.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: List and download server logs with Azure CLI
3-
description: This article describes how to list and download Azure Database for PostgreSQL - Flexible Server logs by using the Azure CLI.
2+
title: Download server logs for Azure Database for PostgreSQL - Flexible Server with Azure CLI
3+
description: This article describes how to download server logs using Azure CLI.
44
ms.service: postgresql
55
ms.subservice: flexible-server
66
author: varun-dhawan
77
ms.author: varundhawan
88
ms.topic: conceptual
9-
ms.date: 1/10/2024
9+
ms.date: 1/16/2024
1010
---
1111

1212
# List and download Azure Database for PostgreSQL - Flexible Server logs by using the Azure CLI

‎articles/postgresql/flexible-server/how-to-server-logs-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'How to enable and download server logs for Azure Database for PostgreSQL - Flexible Server'
2+
title: 'Download server logs for Azure Database for PostgreSQL - Flexible Server'
33
description: This article describes how to download server logs using Azure portal.
44
ms.service: postgresql
55
ms.subservice: flexible-server

‎articles/private-link/how-to-approve-private-link-cross-subscription.md

Lines changed: 158 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,158 @@
1+
---
2+
title: Approve private link connections across subscriptions
3+
titleSuffix: Azure Private Link
4+
description: Get started learning how to approve and manage private link connections across subscriptions with Azure Private Link.
5+
author: asudbring
6+
ms.author: allensu
7+
ms.service: private-link
8+
ms.topic: how-to
9+
ms.date: 01/11/2024
10+
#customer intent: As a Network Administrator, I want the approve private link connections across Azure subscriptions.
11+
12+
---
13+
14+
# Approve private link connections across subscriptions
15+
16+
Azure Private Link enables you to connect privately to Azure resources. Private Link connections are scoped to a specific subscription. This article shows you how to approve a private endpoint connection across subscriptions.
17+
18+
## Prerequisites
19+
20+
- Two active Azure subscriptions.
21+
22+
- One subscription hosts the Azure resource and the other subscription contains the consumer private endpoint and virtual network.
23+
24+
- An administrator account for each subscription or an account with permissions in each subscription to create and manage resources.
25+
26+
Resources used in this article:
27+
28+
| Resource | Subscription | Resource group | Location |
29+
| --- | --- | --- | --- |
30+
| **storage1** *(This name is unique, replace with the name you create)* | subscription-1 | test-rg | East US 2 |
31+
| **vnet-1** | subscription-2 | test-rg | East US 2 |
32+
| **private-endpoint** | subscription-2 | test-rg | East US 2 |
33+
34+
## Sign in to subscription-1
35+
36+
Sign in to **subscription-1** in the [Azure portal](https://portal.azure.com).
37+
38+
## Create a resource group
39+
40+
1. In the search box at the top of the portal, enter **Resource group**. Select **Resource groups** in the search results.
41+
42+
1. Select **+ Create**.
43+
44+
1. In the **Basics** tab of **Create a resource group**, enter or select the following information:
45+
46+
| Setting | Value |
47+
| ------- | ----- |
48+
| **Project details** | |
49+
| Subscription | Select **subscription-1**. |
50+
| Resource group | Enter **test-rg**. |
51+
| Region | Select **East US 2**. |
52+
53+
1. Select **Review + Create**.
54+
55+
1. Select **Create**.
56+
57+
[!INCLUDE [create-storage-account.md](../../includes/create-storage-account.md)]
58+
59+
## Obtain storage account resource ID
60+
61+
You need the storage account resource ID to create the private endpoint connection in **subscription-2**. Use the following steps to obtain the storage account resource ID.
62+
63+
1. In the search box at the top of the portal, enter **Storage account**. Select **Storage accounts** in the search results.
64+
65+
1. Select **storage1** or the name of your existing storage account.
66+
67+
1. In **Settings**, select **Endpoints**.
68+
69+
1. Copy the entry in **Storage account resource ID**.
70+
71+
## Sign in to subscription-2
72+
73+
Sign in to **subscription-2** in the [Azure portal](https://portal.azure.com).
74+
75+
## Register the `Microsoft.Storage` resource provider
76+
77+
For the private endpoint connection to complete successfully, the Microsoft.Storage resource provider must be registered in **subscription-2**. Use the following steps to register the resource provider. If the `Microsoft.Storage` resource provider is already registered, skip this step.
78+
79+
> [!IMPORTANT]
80+
> If you're using a different resource type, you must register the resource provider for that resource type if it's not already registered.
81+
82+
1. In the search box at the top of the portal, enter **Subscription**. Select **Subscriptions** in the search results.
83+
84+
1. Select **subscription-2**.
85+
86+
1. In **Settings**, select **Resource providers**.
87+
88+
1. In the **Resource providers** filter box, enter **Microsoft.Storage**. Select **Microsoft.Storage**.
89+
90+
1. Select **Register**.
91+
92+
[!INCLUDE [virtual-network-create.md](../../includes/virtual-network-create.md)]
93+
94+
## Create private endpoint
95+
96+
1. In the search box at the top of the portal, enter **Private endpoint**. Select **Private endpoints**.
97+
98+
1. Select **+ Create** in **Private endpoints**.
99+
100+
1. In the **Basics** tab of **Create a private endpoint**, enter or select the following information:
101+
102+
| Setting | Value |
103+
| ------- | ----- |
104+
| **Project details** | |
105+
| Subscription | Select **subscription-2**. |
106+
| Resource group | Select **test-rg** |
107+
| **Instance details** | |
108+
| Name | Enter **private-endpoint**. |
109+
| Network Interface Name | Leave the default of **private-endpoint-nic**. |
110+
| Region | Select **East US 2**. |
111+
112+
1. Select **Next: Resource**.
113+
114+
1. Select **Connect to an Azure resource by resource ID or alias**.
115+
116+
1. In **Resource ID or alias**, paste the storage account resource ID that you copied earlier.
117+
118+
1. In **Target sub-resource**, enter **blob**.
119+
120+
1. Select **Next: Virtual Network**.
121+
122+
1. In **Virtual Network**, enter or select the following information:
123+
124+
| Setting | Value |
125+
| ------- | ----- |
126+
| **Networking** | |
127+
| Virtual network | Select **vnet-1 (test-rg)**. |
128+
| Subnet | Select **subnet-1**. |
129+
130+
1. Select **Next: DNS**.
131+
132+
1. Select **Next: Tags**.
133+
134+
1. Select **Review + Create**.
135+
136+
1. Select **Create**.
137+
138+
## Approve private endpoint connection
139+
140+
The private endpoint connection is in a **Pending** state until approved. Use the following steps to approve the private endpoint connection in **subscription-1**.
141+
142+
1. In the search box at the top of the portal, enter **Private endpoint**. Select **Private endpoints**.
143+
144+
1. Select **Pending connections**.
145+
146+
1. Select the box next to your storage account in **subscription-1**.
147+
148+
1. Select **Approve**.
149+
150+
1. Select **Yes** in **Approve connection**.
151+
152+
## Next steps
153+
154+
In this article, you learned how to approve a private endpoint connection across subscriptions. To learn more about Azure Private Link, continue to the following articles:
155+
156+
- [Azure Private Link overview](private-link-overview.md)
157+
158+
- [Azure Private endpoint overview](private-endpoint-overview.md)

‎articles/private-link/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,8 @@
7575
href: /security/benchmark/azure/baselines/azure-private-link-security-baseline?toc=/azure/private-link/toc.json
7676
- name: How-to
7777
items:
78+
- name: Approve private link connections across subscriptions
79+
href: how-to-approve-private-link-cross-subscription.md
7880
- name: Configure an application security group
7981
href: configure-asg-private-endpoint.md
8082
- name: Export private endpoint DNS records

‎includes/notification-hubs-firebase-deprecation.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,17 @@ title: include file
55
author: sethmanheim
66
ms.service: notification-hubs
77
ms.topic: include
8-
ms.date: 12/06/2023
8+
ms.date: 01/16/2024
99
ms.author: sethm
1010
ms.custom: include file
1111
---
1212

13-
> [!IMPORTANT]
14-
> Firebase Cloud Messaging (FCM) is a service that, among other things, facilitates developers sending push notifications to Google Play-supported Android devices. Azure Notification Hubs currently communicates with FCM using the legacy HTTP protocol. FCM v1 is an updated API that offers more features and capabilities. Google announced that they are deprecating FCM legacy HTTP and will stop supporting it on June 20, 2024. Therefore, developers who use Azure Notification Hubs to communicate with Google Play-supported Android devices today, will need to migrate their applications and notification payloads to the newer format. Azure Notification Hubs will continue to support FCM legacy HTTP until Google stops accepting requests. Once the new FCM integration is complete, Azure Notification Hubs will announce when you can begin migrating. For more information, see the [migration steps](#migration-steps) in the next section.
13+
> [!NOTE]
14+
> The core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 are ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you must migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration by March 1, 2024.
15+
>
16+
> To help with this transition, we invite you to join our preview program and test the FCM v1 onboarding process for REST APIs in February 2024. This gives you early access to the new features and capabilities, as well as the opportunity to provide feedback and report any issues.
17+
>
18+
> If you are interested in joining the preview program, [contact us by email](mailto:[email protected]) by January 25, 2024. We will reply with instructions on how to onboard to FCM v1 using the Azure portal or the REST API. You will also receive a link to our documentation and support channels.
1519
1620
## Migration steps
1721

0 commit comments

Comments
 (0)