Skip to content

Commit 83736d1

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into ehub-grid-0818
2 parents dc4cade + cc84b09 commit 83736d1

File tree

1,443 files changed

+17581
-13184
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,443 files changed

+17581
-13184
lines changed

.openpublishing.redirection.json

Lines changed: 71 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,6 +165,12 @@
165165
"redirect_url": "/azure/iot-fundamentals/iot-introduction",
166166
"redirect_document_id": false
167167
},
168+
169+
{
170+
"source_path": "articles/iot-hub/iot-hub-create-using-cli-nodejs.md",
171+
"redirect_url": "/azure/iot-hub/iot-hub-create-using-cli",
172+
"redirect_document_id": true
173+
},
168174
{
169175
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-tutorial-analytics.md",
170176
"redirect_url": "/azure/cognitive-services/custom-decision-service",
@@ -2735,6 +2741,16 @@
27352741
"redirect_url": "/azure/logic-apps/logic-apps-create-deploy-template",
27362742
"redirect_document_id": true
27372743
},
2744+
{
2745+
"source_path": "articles/connectors/connectors-create-api-sharepointserver.md",
2746+
"redirect_url": "/azure/connectors/connectors-create-api-sharepoint",
2747+
"redirect_document_id": true
2748+
},
2749+
{
2750+
"source_path": "articles/connectors/connectors-create-api-sharepointonline.md",
2751+
"redirect_url": "/azure/connectors/connectors-create-api-sharepoint",
2752+
"redirect_document_id": false
2753+
},
27382754
{
27392755
"source_path": "articles/logic-apps/custom-connector-build-web-api-app-tutorial.md",
27402756
"redirect_url": "https://docs.microsoft.com/connectors/custom-connectors/create-web-api-connector",
@@ -12868,6 +12884,11 @@
1286812884
"redirect_url": "./end-user/microsoft-authenticator-app-how-to",
1286912885
"redirect_document_id": false
1287012886
},
12887+
{
12888+
"source_path": "articles/service-fabric/service-fabric-get-started-standalone-cluster.md",
12889+
"redirect_url": "/azure/service-fabric/service-fabric-cluster-creation-for-windows-server",
12890+
"redirect_document_id": false
12891+
},
1287112892
{
1287212893
"source_path": "articles/service-fabric/service-fabric-update-vmss-sku.md",
1287312894
"redirect_url": "/azure/service-fabric/service-fabric-cluster-upgrade",
@@ -25611,6 +25632,11 @@
2561125632
"redirect_url": "/azure/storage/queues/storage-queues-introduction",
2561225633
"redirect_document_id": false
2561325634
},
25635+
{
25636+
"source_path": "articles/storage/data-lake-storage/index.md",
25637+
"redirect_url": "/azure/storage/data-lake-storage/introduction",
25638+
"redirect_document_id": false
25639+
},
2561425640
{
2561525641
"source_path": "articles/dev-spaces/index.md",
2561625642
"redirect_url": "/azure/dev-spaces/azure-dev-spaces",
@@ -26456,6 +26482,26 @@
2645626482
"redirect_url": "/azure/azure-stack/azure-stack-powershell-download",
2645726483
"redirect_document_id": false
2645826484
},
26485+
{
26486+
"source_path": "articles/azure-stack/azure-stack-extension-host-prepare.md",
26487+
"redirect_url": "/azure/azure-stack",
26488+
"redirect_document_id": false
26489+
},
26490+
{
26491+
"source_path": "articles/azure-stack/user/azure-stack-metrics-azure-data.md",
26492+
"redirect_url": "/azure/azure-stack",
26493+
"redirect_document_id": false
26494+
},
26495+
{
26496+
"source_path": "articles/azure-stack/user/azure-stack-metrics-monitor.md",
26497+
"redirect_url": "/azure/azure-stack",
26498+
"redirect_document_id": false
26499+
},
26500+
{
26501+
"source_path": "articles/azure-stack/user/azure-stack-metrics-supported.md",
26502+
"redirect_url": "/azure/azure-stack",
26503+
"redirect_document_id": false
26504+
},
2645926505
{
2646026506
"source_path": "articles/active-directory/application-proxy-teams.md",
2646126507
"redirect_url": "/azure/active-directory/manage-apps/application-proxy-integrate-with-teams",
@@ -27304,12 +27350,36 @@
2730427350
"source_path": "articles/cognitive-services/speech-service/speech-scenarios.md",
2730527351
"redirect_url": "/azure/cognitive-services/speech-service/overview",
2730627352
"redirect_document_id": true
27353+
},
27354+
{
27355+
"source_path": "articles/aks/aks-ssh.md",
27356+
"redirect_url": "/azure/aks/ssh",
27357+
"redirect_document_id": true
2730727358
},
2730827359
{
2730927360
"source_path": "articles/cognitive-services/luis/Home.md",
2731027361
"redirect_url": "/azure/cognitive-services/luis/what-is-luis",
2731127362
"redirect_document_id": true
27363+
},
27364+
{
27365+
"source_path": "articles/data-factory/data-factory-monitor-oms.md",
27366+
"redirect_url": "/azure/data-factory/monitor-using-azure-monitor",
27367+
"redirect_document_id": true
27368+
},
27369+
{
27370+
"source_path": "articles/virtual-machines/linux/ansible-create-complete-vm.md",
27371+
"redirect_url": "/azure/virtual-machines/linux/ansible-create-vm",
27372+
"redirect_document_id": true
27373+
},
27374+
{
27375+
"source_path": "articles/networking/networking-virtual-datacenter.md",
27376+
"redirect_url": "/azure/architecture/vdc/networking-virtual-datacenter",
27377+
"redirect_document_id": true
27378+
},
27379+
{
27380+
"source_path": "articles/security-center/security-center-disk-encryption.md",
27381+
"redirect_url": "/azure/security/azure-security-disk-encryption-overview",
27382+
"redirect_document_id": false
2731227383
}
27313-
2731427384
]
2731527385
}

articles/active-directory/TOC.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@
5454
#### [Admins adding B2B users](b2b/add-users-administrator.md)
5555
#### [Information workers adding B2B users](b2b/add-users-information-worker.md)
5656
#### [API and customization](b2b/customize-invitation-api.md)
57+
#### [Google federation](b2b/google-federation.md)
5758
#### [Code and Azure PowerShell samples](b2b/code-samples.md)
5859
#### [Self-service sign-up portal sample](b2b/self-service-portal.md)
5960
#### [Invitation email](b2b/invitation-email-elements.md)

articles/active-directory/active-directory-tou.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.tgt_pltfrm: na
1212
ms.devlang: na
1313
ms.topic: conceptual
1414
ms.component: compliance
15-
ms.date: 07/31/2018
15+
ms.date: 08/22/2018
1616
ms.author: rolyon
1717

1818
---
@@ -119,6 +119,8 @@ The following screen shows how Terms of use looks on mobile devices.
119119

120120
![Audit Event](media/active-directory-tou/mobile-tou.png)
121121

122+
Users are only required to accept the Terms of use once and they will not see the Terms of use again on subsequent sign ins.
123+
122124
### How users can review their Terms of use
123125
Users can review and see the Terms of use that they have accepted by using the following procedure.
124126

articles/active-directory/application-config-sso-problem-configure-password-sso-gallery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ There are two main causes to this issue:
6464

6565
- Depending on the security settings enabled in Internet Explorer, if the website is not part of a **Trusted Zone**, sometimes our script be blocked from executing for the application.
6666

67-
* To resolve this, instruct the user to **Add the application’s website** to the **Trusted Sites** list within their **Internet Explorer security settings**. You can send your users to the [How to add a site to my trusted sites list](https://answers.microsoft.com/ie/forum/ie9-windows_7/how-do-i-add-a-site-to-my-trusted-sites-list/98cc77c8-b364-e011-8dfc-68b599b31bf5) article for detailed instructions.
67+
* To resolve this, instruct the user to **Add the application’s website** to the **Trusted Sites** list within their **Internet Explorer security settings**. You can send your users to the [How to add a site to my trusted sites list](https://answers.microsoft.com/en-us/ie/forum/ie9-windows_7/how-do-i-add-a-site-to-my-trusted-sites-list/98cc77c8-b364-e011-8dfc-68b599b31bf5) article for detailed instructions.
6868

6969
- In rare circumstances, Internet Explorer’s security validation can sometimes cause the page to load more slowly than the execution of our script.
7070

articles/active-directory/authentication/concept-sspr-writeback.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Password writeback is supported in environments that use:
2222

2323
* [Active Directory Federation Services](../connect/active-directory-aadconnect-federation-management.md)
2424
* [Password hash synchronization](../connect/active-directory-aadconnectsync-implement-password-hash-synchronization.md)
25-
* [Pass-through authentication](/../connect/active-directory-aadconnect-pass-through-authentication.md)
25+
* [Pass-through authentication](../connect/active-directory-aadconnect-pass-through-authentication.md)
2626

2727
Password writeback provides:
2828

@@ -157,4 +157,4 @@ Passwords are *not* written back in any of the following situations:
157157

158158
## Next steps
159159

160-
Enable password writeback using the Tutorial: [Enabling password writeback](tutorial-enable-writeback.md)
160+
Enable password writeback using the Tutorial: [Enabling password writeback](tutorial-enable-writeback.md)
Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
---
2+
3+
title: Add Google as an identity provider for Azure Active Directory B2B | Microsoft Docs
4+
description: Federate with Google to enable guest users to sign in to your Azure AD apps with their own Gmail account
5+
6+
services: active-directory
7+
ms.service: active-directory
8+
ms.component: B2B
9+
ms.topic: article
10+
ms.date: 08/20/2018
11+
12+
ms.author: mimart
13+
author: msmimart
14+
manager: mtillman
15+
ms.reviewer: mal
16+
17+
---
18+
19+
# Add Google as an identity provider for B2B guest users
20+
21+
By setting up federation with Google, you can allow invited users to sign in to your shared apps and resources with their own Google accounts, without having to create Microsoft Accounts (MSAs) or Azure AD accounts.
22+
> [!NOTE]
23+
> Your Google guest users must sign in using a link that includes the tenant context, for example `https://myapps.microsoft.com/?tenantid=<tenant id>`. Direct links to applications and resources also work as long as they include the tenant context. Guest users are currently unable to sign in using endpoints that have no tenant context. For example, using `https://myapps.microsoft.com`, `https://portal.azure.com`, or the Teams common endpoint will result in an error.
24+
25+
## What is the experience for the Google user?
26+
When you send an invitation to a Google Gmail user, the guest user should access your shared apps or resources using a link that includes the tenant context. Their experience varies depending on whether they're already signed in to Google:
27+
- If the guest user is not signed in to Google, they're prompted to sign in to Google.
28+
- If the guest user is already signed in to Google, they'll be prompted to choose the account they want to use. They must choose the account you used to invite them.
29+
30+
If the guest user sees a "header too long" error, they can try clearing their cookies, or they can open a private or incognito window and try signing in again.
31+
32+
![Sign in with Google](media/google-federation/google-sign-in.png)
33+
34+
## Step 1: Configure a Google developer project
35+
First, create a new project in the Google Developers Console to obtain a client ID and a client secret that you can later add to Azure AD.
36+
1. Go to the Google APIs at https://console.developers.google.com, and sign in with your Google account. We recommend that you use a shared team Google account.
37+
2. Create a new project: On the Dashboard, select **Create Project**, and then select **Create**. On the New Project page, enter a **Project Name**, and then select **Create**.
38+
39+
![New Google project](media/google-federation/google-new-project.png)
40+
41+
3. Make sure your new project is selected in the project menu. Then open the menu in the upper left and select **APIs & Services** > **Credentials**.
42+
43+
![Google API credentials](media/google-federation/google-api.png)
44+
45+
4. Choose the **Oauth consent screen** tab and enter a **Product name shown to users**. (Leave the other settings.) Select **Save**.
46+
47+
![Google OAuth consent screen](media/google-federation/google-oauth-consent-screen.png)
48+
49+
5. Choose the **Credentials** tab. In the **Create credentials** menu, choose **OAuth client ID**.
50+
51+
![Google API credentials](media/google-federation/google-api-credentials.png)
52+
53+
6. Under **Application type**, choose **Web application**, and then under **Authorized redirect URIs**, enter the following URIs:
54+
- `https://login.microsoftonline.com`
55+
- `https://login.microsoftonline.com/te/<directory id>/oauth2/authresp` <br>(where `<directory id>` is your directory ID)
56+
57+
> [!NOTE]
58+
> To find your directory ID, go to https://portal.azure.com, and under **Azure Active Directory**, choose **Properties** and copy the **Directory ID**.
59+
60+
![Create OAuth client ID](media/google-federation/google-create-oauth-client-id.png)
61+
62+
7. Select **Create**. Copy the client ID and client secret, which you'll use when you add the identity provider in the Azure AD portal.
63+
64+
![OAuth client ID and client secret](media/google-federation/google-auth-client-id-secret.png)
65+
66+
## Step 2: Configure Google federation in Azure AD
67+
Now you'll set the Google client ID and client secret, either by entering it in the Azure AD portal or by using PowerShell. Be sure to test your Google federation configuration by inviting yourself using a Gmail address and trying to redeem the invitation with your invited Google account.
68+
69+
#### To configure Google federation in the Azure AD portal
70+
1. Go to the [Azure portal](https://portal.azure.com). In the left pane, select **Azure Active Directory**.
71+
2. Select **Organizational Relationships**.
72+
3. Select **Identity providers**, and then click the **Google** button.
73+
4. Enter a name. Then enter the client ID and client secret you obtained earlier. Select **Save**.
74+
75+
![Add Google identity provider](media/google-federation/google-identity-provider.png)
76+
77+
#### To configure Google federation by using PowerShell
78+
1. Install the latest version of the Azure AD PowerShell for Graph module ([AzureADPreview](https://www.powershellgallery.com/packages/AzureADPreview)).
79+
2. Run the following command:
80+
`Connect-AzureAD`.
81+
3. At the sign-in prompt, sign in with the managed Global Administrator account.
82+
4. Run the following command:
83+
84+
`New-AzureADMSIdentityProvider -Type Google -Name Google -ClientId [Client ID] -ClientSecret [Client secret]`
85+
86+
> [!NOTE]
87+
> Use the client id and client secret from the app you created in "Step 1: Configure a Google developer project." For more information, see the [New-AzureADMSIdentityProvider](https://docs.microsoft.com/en-us/powershell/module/azuread/new-azureadmsidentityprovider?view=azureadps-2.0-preview) article.
88+
89+
## How do I remove Google federation?
90+
You can delete your Google federation setup. If you do so, Google guest users who have already redeemed their invitation will not be able to sign in, but you can give them access to your resources again by deleting them from the directory and re-inviting them.
91+
92+
### To delete Google federation in the Azure AD portal:
93+
1. Go to the [Azure portal](https://portal.azure.com). In the left pane, select **Azure Active Directory**.
94+
2. Select **Organizational Relationships**.
95+
3. Select **Identity providers**, and then click the **Google** button.
96+
4. Select **Google**, and then select **Delete**.
97+
98+
![Deleted the social identity provider](media/google-federation/google-social-identity-providers.png)
99+
100+
1. Select **Yes** to confirm deletion.
101+
102+
### To delete Google federation by using PowerShell:
103+
1. Install the latest version of the Azure AD PowerShell for Graph module ([AzureADPreview](https://www.powershellgallery.com/packages/AzureADPreview)).
104+
2. Run `Connect-AzureAD`.
105+
4. In the login in prompt, sign in with the managed Global Administrator account.
106+
5. Enter the following command:
107+
108+
`Remove-AzureADMSIdentityProvider -Id Google-OAUTH`
109+
110+
> [!NOTE]
111+
> For more information, see [Remove-AzureADMSIdentityProvider](https://docs.microsoft.com/en-us/powershell/module/azuread/Remove-AzureADMSIdentityProvider?view=azureadps-2.0-preview).
33.2 KB
Loading
21.9 KB
Loading
12 KB
Loading
98.6 KB
Loading

0 commit comments

Comments
 (0)