Skip to content

Commit 284dfd7

Browse files
authored
Merge branch 'MicrosoftDocs:main' into EmailResourceManagement-PowerShell
2 parents a5f6587 + 1ab53e3 commit 284dfd7

File tree

5 files changed

+10
-5
lines changed

5 files changed

+10
-5
lines changed

articles/backup/backup-azure-database-postgresql-flex-support-matrix.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,23 +21,25 @@ Azure Database for PostgreSQL - Flexible server backup is now available in all p
2121

2222
- PostgreSQL Flexible Server backup data can be recovered in user specified storage containers that can be used to rebuild the PostgreSQL flexible server. You can restore this data as a new PostgreSQL - flexible server with the database native tools.
2323

24-
- Only weekly backups are supported with option to opt for only one day in the week on which backup is initiated.
25-
26-
- Both Cross Region and Cross Subscription backups are supported.
24+
- Backups for the PostgreSQL server are supported when the Backup Vault is in the same or a different subscription as the database, provided they are within the same tenant and region. Restores are supported across regions (Azure Paired) and across subscriptions within the same tenant.
2725

2826
- Recommended limit for the maximum server size is 4 TB.
2927

3028
- PostgreSQL - Flexible servers encrypted by Customer Managed Key are supported.
3129

3230
- Private endpoint-enabled Azure PostgreSQL flexible servers can be backed up by allowing trusted Microsoft services in the network settings.
3331

32+
- Backups for PGSQLFlex will exclude databases owned by `azuresu` or `azure_pg_admin`, including the native `postgres` database. As a result, databases with these owners cannot be backed up or restored.
33+
3434

3535
## Limitation
3636

3737
- Currently, restoring backups directly to flexible server isn't supported.
3838

3939
- Currently, backing up individual databases isn't supported. You can only back up the entire server.
4040

41+
- Only weekly backups are supported with option to opt for only one day in the week on which backup is initiated.
42+
4143

4244
## Next steps
4345

articles/container-apps/gpu-serverless-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Access to this feature is only available after you have serverless GPU quota. Yo
7575
7676
## Supported regions
7777

78-
Serverless GPUs are available in preview in the *West US 3* and *Australia East* regions.
78+
Serverless GPUs are available in preview in the *West US 3*, *Australia East*, and *Sweden Central* regions.
7979

8080
## Use serverless GPUs
8181

articles/container-apps/workload-profiles-overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Profiles are configured to fit the different needs of your applications.
2222
| Profile type | Description | Potential use |
2323
|--|--|--|
2424
| Consumption | Automatically added to any new environment. | Apps that don't require specific hardware requirements |
25+
| Consumption GPU (preview) | Scale-to-zero serverless GPUs are available in West US 3, Australia East, and Sweden Central regions. | Apps that require GPU |
2526
| Dedicated (General purpose) | Balance of memory and compute resources | Apps that require larger amounts of CPU and/or memory |
2627
| Dedicated (Memory optimized) | Increased memory resources | Apps that need access to large in-memory data, in-memory machine learning models, or other high memory requirements |
2728
| Dedicated (GPU enabled) (preview) | GPU enabled with increased memory and compute resources available in West US 3 and North Europe regions. | Apps that require GPU |

articles/trusted-signing/faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ sections:
5252
- Follow the steps to present your existing VID for Trusted Signing. For this process, VIDs must include your address in addition to your name. Ensure that your VIDs have your address on them before using them for Trusted Signing.
5353
- question: What if I need assistance with identity validation?
5454
answer: |
55-
- For questions about identity validation in Trusted Signing, contact us by using [Microsoft Q&A](https://learn.microsoft.com/answers/tags/509/trusted-signing) (use the tag **Azure Trusted Signing**) or [Stack Overflow](https://stackoverflow.com/questions/tagged/trusted-signing) (use the tag **trusted-signing**). Azure support doesn't resolve identity validation issues for Trusted Signing.
55+
- For questions about identity validation in Trusted Signing, contact us via Azure Support or by using [Microsoft Q&A](https://learn.microsoft.com/answers/tags/509/trusted-signing) (use the tag **Azure Trusted Signing**).
5656
- question: What is the cost of using Trusted Signing?
5757
answer: |
5858
- For pricing information, see [Trusted Signing pricing](https://azure.microsoft.com/pricing/details/trusted-signing/).

articles/trusted-signing/quickstart.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -209,6 +209,8 @@ You can complete your own identity validation by filling in the request form wit
209209

210210
> [!NOTE]
211211
> You can't create an identity validation request if you aren't assigned the appropriate role. If the **New identity** button on the menu bar appears dimmed in the Azure portal, ensure that you are assigned the Trusted Signing Identity Verifier role to proceed with identity validation.
212+
> [!NOTE]
213+
> At this time Trusted Signing can only onboard organizations that were incorporated more than 3 years ago.
212214
213215
# [Identity Validation - Organization](#tab/orgvalidation)
214216

0 commit comments

Comments
 (0)