Skip to content

Commit e17d88a

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into bas1
2 parents a8c64e3 + 1e3ffd7 commit e17d88a

File tree

8 files changed

+104
-89
lines changed

8 files changed

+104
-89
lines changed

articles/api-management/api-management-howto-aad-b2c.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Azure Active Directory B2C is a cloud identity management solution for consumer-
5656

5757
![Register a new application 3][api-management-howto-aad-b2c-app-details]
5858

59-
1. If you're using the new developer portal (not the legacy developer portal), include the **Given Name**, **Surname**, and **User's Object Id** in the application claims.
59+
1. If you're using the new developer portal (not the legacy developer portal), include the **Given Name**, **Surname**, and **User's Object ID** in the application claims.
6060

6161
![Application claims](./media/api-management-howto-aad-b2c/api-management-application-claims.png)
6262

@@ -88,12 +88,12 @@ Azure Active Directory B2C is a cloud identity management solution for consumer-
8888

8989
## Developer portal - add Azure AD B2C account authentication
9090

91-
In the developer portal, sign-in with AAD B2C is possible with the **OAuth buttons** widget. The widget is already included on the sign-in page of the default developer portal content.
92-
93-
![AAD buttons widget](./media/api-management-howto-aad/portal-oauth-widget.png)
91+
In the developer portal, sign-in with AAD B2C is possible with the **Sign-in button: OAuth** widget. The widget is already included on the sign-in page of the default developer portal content.
9492

9593
Although a new account will be automatically created whenever a new user signs in with AAD B2C, you may consider adding the same widget to the sign-up page.
9694

95+
The **Sign-up form: OAuth** widget represents a form used for signing up with OAuth.
96+
9797
> [!IMPORTANT]
9898
> You need to [republish the portal](api-management-howto-developer-portal-customize.md#publish) for the AAD changes to take effect.
9999

articles/api-management/api-management-howto-aad.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -49,10 +49,10 @@ This article shows you how to enable access to the developer portal for users fr
4949
12. Under **Manage**, select **App registrations**.
5050
13. Select **New registration**. On the **Register an application** page, set the values as follows:
5151

52-
* Set **Name** to a meaningful name. e.g., *developer-portal*
53-
* Set **Supported account types** to **Accounts in this organizational directory only**.
54-
* Set **Redirect URI** to the value you got from step 9.
55-
* Choose **Register**.
52+
* Set **Name** to a meaningful name. e.g., *developer-portal*
53+
* Set **Supported account types** to **Accounts in this organizational directory only**.
54+
* Set **Redirect URI** to the value you got from step 9.
55+
* Choose **Register**.
5656

5757
14. After the application is registered, copy the **Application (client) ID** from the **Overview** page.
5858
15. Go back to your API Management instance. In the **Add identity provider** window, paste the **Application (client) ID** value into the **Client ID** box.
@@ -67,11 +67,11 @@ This article shows you how to enable access to the developer portal for users fr
6767
6868
19. The **Add identity provider** window also contains the **Allowed Tenants** text box. There, specify the domains of the Azure AD instances to which you want to grant access to the APIs of the API Management service instance. You can separate multiple domains with newlines, spaces, or commas.
6969

70-
> [!NOTE]
71-
> You can specify multiple domains in the **Allowed Tenants** section. Before any user can sign in from a different domain than the original domain where the application was registered, a global administrator of the different domain must grant permission for the application to access directory data. To grant permission, the global administrator should:
72-
> a. Go to `https://<URL of your developer portal>/aadadminconsent` (for example, https://contoso.portal.azure-api.net/aadadminconsent).
73-
> b. Type in the domain name of the Azure AD tenant that they want to give access to.
74-
> c. Select **Submit**.
70+
> [!NOTE]
71+
> You can specify multiple domains in the **Allowed Tenants** section. Before any user can sign in from a different domain than the original domain where the application was registered, a global administrator of the different domain must grant permission for the application to access directory data. To grant permission, the global administrator should:
72+
> a. Go to `https://<URL of your developer portal>/aadadminconsent` (for example, https://contoso.portal.azure-api.net/aadadminconsent).
73+
> b. Type in the domain name of the Azure AD tenant that they want to give access to.
74+
> c. Select **Submit**.
7575
7676
20. After you specify the desired configuration, select **Add**.
7777

@@ -92,7 +92,7 @@ Now you can add external Azure AD groups from the **Groups** tab of your API Man
9292

9393
1. Select the **Groups** tab.
9494
2. Select the **Add AAD group** button.
95-
!["Add AAD group" button](./media/api-management-howto-aad/api-management-with-aad008.png)
95+
!["Add AAD group" button](./media/api-management-howto-aad/api-management-with-aad008.png)
9696
3. Select the group that you want to add.
9797
4. Press the **Select** button.
9898

@@ -102,12 +102,12 @@ Users from the configured Azure AD instance can now sign in to the developer por
102102

103103
## <a id="log_in_to_dev_portal"/> Developer portal - add Azure AD account authentication
104104

105-
In the developer portal, sign-in with AAD is possible with the **OAuth buttons** widget. The widget is already included on the sign-in page of the default developer portal content.
106-
107-
![AAD buttons widget](./media/api-management-howto-aad/portal-oauth-widget.png)
105+
In the developer portal, sign-in with AAD is possible with the **Sign-in button: OAuth** widget. The widget is already included on the sign-in page of the default developer portal content.
108106

109107
Although a new account will be automatically created whenever a new user signs in with AAD, you may consider adding the same widget to the sign-up page.
110108

109+
The **Sign-up form: OAuth** widget represents a form used for signing up with OAuth.
110+
111111
> [!IMPORTANT]
112112
> You need to [republish the portal](api-management-howto-developer-portal-customize.md#publish) for the AAD changes to take effect.
113113
Binary file not shown.

articles/backup/backup-support-matrix-iaas.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Here's how you can back up and restore Azure VMs with the Azure Backup service.
2121

2222
**Scenario** | **Backup** | **Agent** |**Restore**
2323
--- | --- | --- | ---
24-
Direct backup of Azure VMs | Back up the entire VM. | No agent is needed on the Azure VM. Azure Backup installs and uses an extension to the [Azure VM agent](https://docs.microsoft.com/azure/virtual-machines/extensions/agent-windows) that is running on the VM. | Restore as follows:<br/><br/> - **Create a basic VM**. This is useful if the VM has no special configuration such as multiple IP addresses.<br/><br/> - **Restore the VM disk**. Restore the disk. Then attach it to an existing VM, or create a new VM from the disk by using PowerShell.<br/><br/> - **Replace VM disk**. If a VM exists and it uses managed disks (unencrypted), you can restore a disk and use it to replace an existing disk on the VM.<br/><br/> - **Restore specific files/folders**. You can restore files/folders from a VM instead of from the entire VM.
24+
Direct backup of Azure VMs | Back up the entire VM. | No additional agent is needed on the Azure VM. Azure Backup installs and uses an extension to the [Azure VM agent](https://docs.microsoft.com/azure/virtual-machines/extensions/agent-windows) that is running on the VM. | Restore as follows:<br/><br/> - **Create a basic VM**. This is useful if the VM has no special configuration such as multiple IP addresses.<br/><br/> - **Restore the VM disk**. Restore the disk. Then attach it to an existing VM, or create a new VM from the disk by using PowerShell.<br/><br/> - **Replace VM disk**. If a VM exists and it uses managed disks (unencrypted), you can restore a disk and use it to replace an existing disk on the VM.<br/><br/> - **Restore specific files/folders**. You can restore files/folders from a VM instead of from the entire VM.
2525
Direct backup of Azure VMs (Windows only) | Back up specific files/folders/volume. | Install the [Azure Recovery Services agent](backup-azure-file-folder-backup-faq.md).<br/><br/> You can run the MARS agent alongside the backup extension for the Azure VM agent to back up the VM at file/folder level. | Restore specific folders/files.
2626
Back up Azure VM to backup server | Back up files/folders/volumes; system state/bare metal files; app data to System Center DPM or to Microsoft Azure Backup Server (MABS).<br/><br/> DPM/MABS then backs up to the backup vault. | Install the DPM/MABS protection agent on the VM. The MARS agent is installed on DPM/MABS.| Restore files/folders/volumes; system state/bare metal files; app data.
2727

0 commit comments

Comments
 (0)