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: articles/active-directory-b2c/identity-provider-swissid.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ In this article, you learn how to provide sign-up and sign-in to customers with
29
29
30
30
To enable sign-in for users with a SwissID account in Azure AD B2C, you need to create an application. To create SwissID application, follow these steps:
31
31
32
-
1. Contact [SwissID Business Partner support](https://www.swissid.ch/en/b2b-kontakt.html).
32
+
1. Contact [SwissID Business Partner support](https://www.swissid.ch/en/b2c-kontakt.html).
33
33
1. After the sign up with SwissID, provide information about your Azure AD B2C tenant:
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/whats-new-docs.md
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,30 @@ manager: CelesteDG
15
15
16
16
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Azure Active Directory](../active-directory/fundamentals/whats-new.md).
Copy file name to clipboardExpand all lines: articles/active-directory/develop/whats-new-docs.md
+18-23Lines changed: 18 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: active-directory
6
6
author: mmacy
7
7
manager: CelesteDG
8
8
9
-
ms.date: 12/06/2021
9
+
ms.date: 01/03/2022
10
10
ms.service: active-directory
11
11
ms.subservice: develop
12
12
ms.topic: reference
@@ -19,6 +19,23 @@ ms.custom: has-adal-ref
19
19
20
20
Welcome to what's new in the Microsoft identity platform documentation. This article lists new docs that have been added and those that have had significant updates in the last three months.
21
21
22
+
## December 2021
23
+
24
+
### New articles
25
+
26
+
-[Build Zero Trust-ready apps using Microsoft identity platform features and tools](zero-trust-for-developers.md)
27
+
-[Quickstart: Sign in users in single-page apps (SPA) using the auth code flow](single-page-app-quickstart.md)
-[Quickstart: Sign in and get an access token in an Angular SPA using the auth code flow](quickstart-v2-javascript-auth-code-angular.md)
37
+
-[Token cache serialization in MSAL.NET](msal-net-token-cache-serialization.md)
38
+
22
39
## November 2021
23
40
24
41
### Updated articles
@@ -51,25 +68,3 @@ Welcome to what's new in the Microsoft identity platform documentation. This art
51
68
-[Microsoft Graph API](microsoft-graph-intro.md)
52
69
-[Microsoft identity platform and the OAuth 2.0 client credentials flow](v2-oauth2-client-creds-grant-flow.md)
53
70
-[What's new for authentication?](reference-breaking-changes.md)
54
-
55
-
## September 2021
56
-
57
-
### New articles
58
-
59
-
-[Desktop app that calls web APIs: Acquire a token interactively](scenario-desktop-acquire-token-interactive.md)
60
-
-[Desktop app that calls web APIs: Acquire a token using Device Code flow](scenario-desktop-acquire-token-device-code-flow.md)
61
-
-[Desktop app that calls web APIs: Acquire a token using Integrated Windows Authentication](scenario-desktop-acquire-token-integrated-windows-authentication.md)
62
-
-[Desktop app that calls web APIs: Acquire a token using Username and Password](scenario-desktop-acquire-token-username-password.md)
63
-
-[Desktop app that calls web APIs: Acquire a token using WAM](scenario-desktop-acquire-token-wam.md)
64
-
-[Implement role-based access control in apps](howto-implement-rbac-for-apps.md)
65
-
-[Migrate public client applications from ADAL.NET to MSAL.NET](msal-net-migration-public-client.md)
66
-
67
-
### Updated articles
68
-
69
-
-[Enhance security with the principle of least privilege](secure-least-privileged-access.md)
70
-
-[Migrate confidential client applications from ADAL.NET to MSAL.NET](msal-net-migration-confidential-client.md)
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/configure-risk-based-step-up-consent.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,8 @@ For example, consent requests for newly registered multi-tenant apps that are no
23
23
24
24
When a risky consent request is detected, the consent prompt displays a message that indicates that admin approval is needed. If the [admin consent request workflow](configure-admin-consent-workflow.md) is enabled, the user can send the request to an admin for further review directly from the consent prompt. If the admin consent request workflow isn't enabled, the following message is displayed:
25
25
26
-
> "**AADSTS90094**: \<clientAppDisplayName> needs permission to access resources in your organization that only an admin can grant. Request an admin to grant permission to this app before you can use it."
26
+
> **AADSTS90094**: \<clientAppDisplayName> needs permission to access resources in your organization that only an admin can grant. Request an admin to grant permission to this app before you can use it.
27
+
27
28
In this case, an audit event is also logged with a category of "ApplicationManagement," an activity type of "Consent to application," and a status reason of "Risky application detected."
Now, you can add the storage output binding to your project.
79
+
78
80
::: zone-end
79
81
80
82
::: zone pivot="programming-language-csharp"
@@ -83,8 +85,6 @@ Extension bundles usage is enabled in the host.json file at the root of the proj
83
85
84
86
::: zone-end
85
87
86
-
Now, you can add the storage output binding to your project.
87
-
88
88
## Add an output binding
89
89
90
90
In Functions, each type of binding requires a `direction`, `type`, and a unique `name` to be defined in the function.json file. The way you define these attributes depends on the language of your function app.
Copy file name to clipboardExpand all lines: articles/backup/backup-support-matrix-iaas.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ For Azure VM Linux backups, Azure Backup supports the list of Linux [distributio
81
81
- Azure Backup doesn't support Core OS Linux.
82
82
- Azure Backup doesn't support 32-bit operating systems.
83
83
- Other bring-your-own Linux distributions might work as long as the [Azure VM agent for Linux](../virtual-machines/extensions/agent-linux.md) is available on the VM, and as long as Python is supported.
84
-
- Azure Backup doesn't support a proxy-configured Linux VM if it doesn't have Python version 2.7 installed.
84
+
- Azure Backup doesn't support a proxy-configured Linux VM if it doesn't have Python version 2.7 or higher installed.
85
85
- Azure Backup doesn't support backing up NFS files that are mounted from storage, or from any other NFS server, to Linux or Windows machines. It only backs up disks that are locally attached to the VM.
86
86
87
87
## Support matrix for managed pre-post scripts for Linux databases
Copy file name to clipboardExpand all lines: articles/backup/tutorial-sap-hana-restore-cli.md
+69-6Lines changed: 69 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,11 @@
2
2
title: Tutorial - SAP HANA DB restore on Azure using CLI
3
3
description: In this tutorial, learn how to restore SAP HANA databases running on an Azure VM from an Azure Backup Recovery Services vault using Azure CLI.
4
4
ms.topic: tutorial
5
-
ms.date: 12/4/2019
5
+
ms.date: 12/23/2021
6
6
ms.custom: devx-track-azurecli
7
+
author: v-amallick
8
+
ms.service: backup
9
+
ms.author: v-amallick
7
10
---
8
11
9
12
# Tutorial: Restore SAP HANA databases in an Azure VM using Azure CLI
@@ -21,11 +24,11 @@ By the end of this tutorial you'll be able to:
21
24
22
25
This tutorial assumes you have an SAP HANA database running on Azure VM that's backed-up using Azure Backup. If you've used [Back up an SAP HANA database in Azure using CLI](tutorial-sap-hana-backup-cli.md) to back up your SAP HANA database, then you're using the following resources:
23
26
24
-
*a resource group named *saphanaResourceGroup*
25
-
*a vault named *saphanaVault*
26
-
*protected container named *VMAppContainer;Compute;saphanaResourceGroup;saphanaVM*
27
-
*backed-up database/item named *saphanadatabase;hxe;hxe*
28
-
*resources in the *westus2* region
27
+
*A resource group named *saphanaResourceGroup*
28
+
*A vault named *saphanaVault*
29
+
*Protected container named *VMAppContainer;Compute;saphanaResourceGroup;saphanaVM*
30
+
*Backed-up database/item named *saphanadatabase;hxe;hxe*
31
+
*Resources in the *westus2* region
29
32
30
33
## View restore points for a backed-up database
31
34
@@ -168,6 +171,66 @@ Name Resource
168
171
169
172
The response will give you the job name. This job name can be used to track the job status using the [az backup job show](/cli/azure/backup/job#az_backup_job_show) cmdlet.
170
173
174
+
## Restore to secondary region
175
+
176
+
To restore a database to the secondary region, specify a target vault and server located in the secondary region, in the restore configuration.
177
+
178
+
```azurecli-interactive
179
+
az backup recoveryconfig show --resource-group saphanaResourceGroup \
Use this recovery configuration in the [az restore restore-azurewl](/cli/azure/backup/restore#az_backup_restore_restore_azurewl) cmdlet. Select the `--use-secondary-region` flag to restore the database to the secondary region.
217
+
218
+
```azurecli-interactive
219
+
az backup restore restore-azurewl --resource-group saphanaResourceGroup \
220
+
--vault-name saphanaVault \
221
+
--recovery-config recoveryconfig.json \
222
+
--use-secondary-region \
223
+
--output table
224
+
```
225
+
226
+
The output will be as follows:
227
+
228
+
```output
229
+
Name Operation Status Item Name Backup Management Type Start Time UTC Duration
To restore the backup data as files instead of a database, we'll use **RestoreAsFiles** as the restore mode. Then choose the restore point, which can either be a previous point-in-time or any of the previous restore points. Once the files are dumped to a specified path, you can take these files to any SAP HANA machine where you want to restore them as a database. Because you can move these files to any machine, you can now restore the data across subscriptions and regions.
Copy file name to clipboardExpand all lines: articles/hdinsight/hdinsight-release-notes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ If you would like to subscribe on release notes, watch releases on [this GitHub
17
17
18
18
## Release date: 12/27/2021
19
19
20
-
This release applies for both HDInsight 4.0. HDInsight release is made available to all regions over several days. The release date here indicates the first region release date. If you don't see below changes, wait for the release being live in your region over several days.
20
+
This release applies for HDInsight 4.0. HDInsight release is made available to all regions over several days. The release date here indicates the first region release date. If you don't see below changes, wait for the release being live in your region over several days.
0 commit comments