Skip to content

Commit e0e9bbc

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into digital-twins-includes-refactor
2 parents 7c3080e + 65ef894 commit e0e9bbc

File tree

1,450 files changed

+7650
-6050
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,450 files changed

+7650
-6050
lines changed

.openpublishing.publish.config.json

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -224,11 +224,29 @@
224224
"branch": "master",
225225
"branch_mapping": {}
226226
},
227+
{
228+
"path_to_root": "samples-qnamaker-go",
229+
"url": "https://github.com/Azure-Samples/cognitive-services-qnamaker-go",
230+
"branch": "master",
231+
"branch_mapping": {}
232+
},
227233
{
228234
"path_to_root": "samples-qnamaker-csharp",
229235
"url": "https://github.com/Azure-Samples/cognitive-services-qnamaker-csharp",
230236
"branch": "master",
231237
"branch_mapping": {}
238+
},
239+
{
240+
"path_to_root": "samples-qnamaker-java",
241+
"url": "https://github.com/Azure-Samples/cognitive-services-qnamaker-java",
242+
"branch": "master",
243+
"branch_mapping": {}
244+
},
245+
{
246+
"path_to_root": "samples-qnamaker-python",
247+
"url": "https://github.com/Azure-Samples/cognitive-services-qnamaker-python",
248+
"branch": "master",
249+
"branch_mapping": {}
232250
}
233251
],
234252
"branch_target_mapping": {

.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1271,6 +1271,16 @@
12711271
"redirect_url": "/azure/iot-edge/quickstart",
12721272
"redirect_document_id": false
12731273
},
1274+
{
1275+
"source_path": "articles/iot-edge/quickstart.experimental.md",
1276+
"redirect_url": "/azure/iot-edge/quickstart",
1277+
"redirect_document_id": false
1278+
},
1279+
{
1280+
"source_path": "articles/iot-edge/quickstart-linux.experimental.md",
1281+
"redirect_url": "/azure/iot-edge/quickstart-linux",
1282+
"redirect_document_id": false
1283+
},
12741284
{
12751285
"source_path": "articles/iot-edge/how-iot-edge-works.md",
12761286
"redirect_url": "/azure/iot-edge/about-iot-edge",
@@ -13765,6 +13775,11 @@
1376513775
"redirect_url": "./end-user/microsoft-authenticator-app-how-to",
1376613776
"redirect_document_id": false
1376713777
},
13778+
{
13779+
"source_path": "articles/service-fabric/service-fabric-patterns-and-scenarios.md",
13780+
"redirect_url": "/azure/service-fabric/service-fabric-application-scenarios",
13781+
"redirect_document_id": false
13782+
},
1376813783
{
1376913784
"source_path": "articles/service-fabric-mesh/service-fabric-mesh-howto-deploy-app-private-registry.md",
1377013785
"redirect_url": "/azure/service-fabric-mesh/service-fabric-mesh-tutorial-template-deploy-app",

articles/active-directory-b2c/active-directory-b2c-custom-setup-adfs2016-idp.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: mtillman
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 09/20/2018
11+
ms.date: 11/05/2018
1212
ms.author: davidmu
1313
ms.component: B2C
1414
---
@@ -60,6 +60,7 @@ You can define an ADFS account as a claims provider by adding it to the **Claims
6060
<Metadata>
6161
<Item Key="WantsEncryptedAssertions">false</Item>
6262
<Item Key="PartnerEntity">https://your-ADFS-domain/federationmetadata/2007-06/federationmetadata.xml</Item>
63+
<Item Key=" XmlSignatureAlgorithm">Sha256</Item>
6364
</Metadata>
6465
<CryptographicKeys>
6566
<Key Id="SamlAssertionSigning" StorageReferenceId="B2C_1A_ADFSSamlCert"/>
@@ -161,6 +162,15 @@ Open a browser and navigate to the URL. Make sure you type the correct URL and t
161162
9. Select **Add Rule**.
162163
10. In **Claim rule template**, select **Send LDAP attributes as claims**.
163164
11. Provide a **Claim rule name**. For the **Attribute store**, select **Select Active Directory**, add the following claims, then click **Finish** and **OK**.
165+
166+
| LDAP attrubute | Outgoing claim type |
167+
| -------------- | ------------------- |
168+
| User-Principal-Name | userPricipalName |
169+
| Surname | family_name |
170+
| Given-Name | given_name |
171+
| E-Mail-Address | email |
172+
| Display-Name | name |
173+
164174
12. Based on your certificate type, you may need to set the HASH algorithm. On the relying party trust (B2C Demo) properties window, select the **Advanced** tab and change the **Secure hash algorithm** to `SHA-1` or `SHA-256`, and click **Ok**.
165175
13. In Server Manager, select **Tools**, and then select **ADFS Management**.
166176
14. Select the relying party trust you created, select **Update from Federation Metadata**, and then click **Update**.

articles/active-directory-b2c/active-directory-b2c-support-create-directory.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ If you encounter issues when you [create an Azure Active Directory B2C (Azure AD
2424
* If the Azure AD B2C tenant doesn't show up in your list of tenants, try again to create the tenant.
2525
* If the Azure AD B2C tenant does show up in your list of tenants and you see the following error message, delete the tenant and create it again:
2626

27-
"Could not complete the creation of the B2C tenant 'contosob2c'. Please visit this [link](http://go.microsoft.com/fwlink/?LinkID=624192&clcid=0x409) for more guidance."
27+
"Could not complete the creation of the B2C tenant 'contosob2c'. Please visit this [link](https://go.microsoft.com/fwlink/?LinkID=624192&clcid=0x409) for more guidance."
2828
* There are known issues when you delete an existing Azure AD B2C tenant and re-create it by using the same domain name. When you create a new Azure AD B2C tenant, you must use a different domain name.
2929
* If these resolutions don't work, contact Azure Support. For more information, see [File support requests for Azure AD B2C](active-directory-b2c-support.md).
3030

articles/active-directory-b2c/b2clogin.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,16 @@ Your Azure AD B2C application probably refers to `login.microsoftonline.com` in
5858

5959
If you're using MSAL, set the **ValidateAuthority** to `false`. The following example shows how you might set the property:
6060

61+
In [MSAL for .Net](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet):
62+
6163
```CSharp
64+
ConfidentialClientApplication client = new ConfidentialClientApplication(...); // can also be PublicClientApplication
65+
client.ValidateAuthority = false;
66+
```
67+
68+
And in [MSAL for Javascript](https://github.com/AzureAD/microsoft-authentication-library-for-js):
69+
70+
```Javascript
6271
this.clientApplication = new UserAgentApplication(
6372
env.auth.clientId,
6473
env.auth.loginAuthority,
@@ -68,5 +77,3 @@ this.clientApplication = new UserAgentApplication(
6877
}
6978
);
7079
```
71-
72-
For more information, see [ClientApplicationBase Class ](https://docs.microsoft.com/dotnet/api/microsoft.identity.client.clientapplicationbase?view=azure-dotnet).

articles/active-directory-b2c/solution-articles.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article gives you links to solution and training information t
44
services: active-directory-b2c
55
author: davidmu1
66
ms.author: davidmu
7-
ms.date: 10/11/2018
7+
ms.date: 11/05/2018
88
ms.topic: conceptual
99
ms.service: active-directory
1010
ms.component: b2c
@@ -22,3 +22,4 @@ Azure Active Directory (Azure AD) B2C enables organizations to implement busines
2222
| [Enabling partners, Suppliers, and Customers to Access Applications with Azure active Directory](https://aka.ms/aadexternalidentities) | Every organization’s success, regardless of its size, industry, or compliance and security posture, relies on organizational ability to collaborate with other organizations and connect with customers.<br><br>Bringing together Azure AD, Azure AD B2C, and Azure AD B2B Collaboration, this guide details the business value and the mechanics of building an application or web experience that provides a consolidated authentication experience tailored to the contexts of your employees, business partners and suppliers, and customers. |
2323
| [Migrating Application Authentication to Azure AD B2C in a Hybrid Environment](https://aka.ms/MigratetoAADB2C) | In today’s modern organizations, digital transformation and moving to the cloud happens in stages, requiring most organizations to at least temporarily operate in a hybrid identity environment.<br><br>This guide focuses on creating the migration plan for moving your first application to Azure AD B2C, and covers the considerations for doing so while in a hybrid identity environment. |
2424
| [General Data protection Regulation (GDPR) Considerations for Customer Facing Applications](https://aka.ms/AADB2CandGDPR) | For any customer facing applications, GDPR must be taken into consideration by all organizations that embark on projects that hold personal data and serve EU citizens.<br><br>This solution guide focuses on how Azure AD B2C can be used as a flexible component of your overall GDPR compliance approach, including how Azure AD B2C components support each of the key GDPR rights for individuals. |
25+
| Working with custom policies:<br><ul><li>[Custom policies introduction](http://download.microsoft.com/download/3/6/1/36187D50-A693-4547-848A-176F17AE1213/Deep%20Dive%20on%20Azure%20AD%20B2C%20Custom%20Policies/Azure%20AD%20B2C%20Custom%20Policies%20-%20Introduction.pdf)</li><li>[Leverage custom policies in your tenant](http://download.microsoft.com/download/3/6/1/36187D50-A693-4547-848A-176F17AE1213/Deep%20Dive%20on%20Azure%20AD%20B2C%20Custom%20Policies/Azure%20AD%20B2C%20Custom%20Policies%20-%20Leveraging%20Custom%20Policies%20for%20your%20Tenant.pdf)</li><li>[Structure policies and manage keys](http://download.microsoft.com/download/3/6/1/36187D50-A693-4547-848A-176F17AE1213/Deep%20Dive%20on%20Azure%20AD%20B2C%20Custom%20Policies/Azure%20AD%20B2C%20Custom%20Policies%20-%20Structuring%20Policies%20and%20Managing%20Keys.pdf)</li><li>[Bring your own identity and migrate users](http://download.microsoft.com/download/3/6/1/36187D50-A693-4547-848A-176F17AE1213/Deep%20Dive%20on%20Azure%20AD%20B2C%20Custom%20Policies/Azure%20AD%20B2C%20Custom%20Policies%20-%20Bring-your-own-identity%20and%20Migrating%20Users.pdf)</li><li>[Troubleshoot policies and audit access](http://download.microsoft.com/download/3/6/1/36187D50-A693-4547-848A-176F17AE1213/Deep%20Dive%20on%20Azure%20AD%20B2C%20Custom%20Policies/Azure%20AD%20B2C%20Custom%20Policies%20-%20Troubleshooting%20Policies%20and%20Auditing.pdf)</li><li>[Deep dive on custom policy schema](http://download.microsoft.com/download/3/6/1/36187D50-A693-4547-848A-176F17AE1213/Deep%20Dive%20on%20Azure%20AD%20B2C%20Custom%20Policies/Azure%20AD%20B2C%20Custom%20Policies%20-%20Deep%20Dive%20on%20Custom%20Policy%20Schema.pdf)</li><br>| This series of documents provides an end-to-end journey with the custom policies in Azure AD B2C, presenting in-depth the most common advanced identity scenarios.<br><br> It includes how to implement and manage custom policies for these scenarios and how to diagnose them with the available tooling. It also provides an in-depth understanding of how custom policies work and details how to fine-tune them to accommodate your own specific requirements. |

articles/active-directory-domain-services/TOC.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22

33
# Overview
44
## [What is Azure AD Domain Services?](active-directory-ds-overview.md)
5+
## [FAQs](active-directory-ds-faqs.md)
56
## Is it right for you?
67
### [Compare with Windows Server AD](active-directory-ds-comparison.md)
78
### [Compare with Azure AD join](active-directory-ds-compare-with-azure-ad-join.md)
@@ -55,7 +56,6 @@
5556
## [Troubleshoot secure LDAP](active-directory-ds-ldaps-troubleshoot.md)
5657

5758
# Troubleshoot
58-
## [FAQs](active-directory-ds-faqs.md)
5959
## [Troubleshooting guide](active-directory-ds-troubleshooting.md)
6060
## [Troubleshoot alerts](active-directory-ds-troubleshoot-alerts.md)
6161
### [Fix a broken NSG configuration](active-directory-ds-troubleshoot-nsg.md)

articles/active-directory-domain-services/active-directory-ds-admin-guide-administer-domain.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ The first step is to set up a Windows Server virtual machine that is joined to t
5959
### Remotely administer the managed domain from a client computer (for example, Windows 10)
6060
The instructions in this article use a Windows Server virtual machine to administer the AAD-DS managed domain. However, you can also choose to use a Windows client (for example, Windows 10) virtual machine to do so.
6161

62-
You can [install Remote Server Administration Tools (RSAT)](http://social.technet.microsoft.com/wiki/contents/articles/2202.remote-server-administration-tools-rsat-for-windows-client-and-windows-server-dsforum2wiki.aspx) on a Windows client virtual machine by following the instructions on TechNet.
62+
You can [install Remote Server Administration Tools (RSAT)](https://social.technet.microsoft.com/wiki/contents/articles/2202.remote-server-administration-tools-rsat-for-windows-client-and-windows-server-dsforum2wiki.aspx) on a Windows client virtual machine by following the instructions on TechNet.
6363

6464
## Task 2 - Install Active Directory administration tools on the virtual machine
6565
Complete the following steps to install the Active Directory Administration tools on the domain joined virtual machine. See Technet for more [information on installing and using Remote Server Administration Tools](https://technet.microsoft.com/library/hh831501.aspx).

articles/active-directory-domain-services/active-directory-ds-admin-guide-configure-secure-ldap.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.workload: identity
1414
ms.tgt_pltfrm: na
1515
ms.devlang: na
1616
ms.topic: conceptual
17-
ms.date: 09/25/2018
17+
ms.date: 11/02/2018
1818
ms.author: ergreenl
1919

2020
---
@@ -41,7 +41,7 @@ Acquire a valid certificate per the following guidelines, before you enable secu
4141

4242
1. **Trusted issuer** - The certificate must be issued by an authority trusted by computers connecting to the managed domain using secure LDAP. This authority may be a public certification authority (CA) or an Enterprise CA trusted by these computers.
4343
2. **Lifetime** - The certificate must be valid for at least the next 3-6 months. Secure LDAP access to your managed domain is disrupted when the certificate expires.
44-
3. **Subject name** - The subject name on the certificate must be your managed domain name. For instance, if your domain is named 'contoso100.com', the certificate's subject name must be 'contoso100.com'.
44+
3. **Subject name** - The subject name on the certificate must be your managed domain. For instance, if your domain is named 'contoso100.com', the certificate's subject name must be 'contoso100.com'. Set the DNS name (subject alternate name) to a wildcard name for your managed domain.
4545
4. **Key usage** - The certificate must be configured for the following uses - Digital signatures and key encipherment.
4646
5. **Certificate purpose** - The certificate must be valid for SSL server authentication.
4747

@@ -79,7 +79,7 @@ On your Windows computer, open a new PowerShell window as **Administrator** and
7979
$lifetime=Get-Date
8080
New-SelfSignedCertificate -Subject contoso100.com `
8181
-NotAfter $lifetime.AddDays(365) -KeyUsage DigitalSignature, KeyEncipherment `
82-
-Type SSLServerAuthentication -DnsName *.contoso100.com
82+
-Type SSLServerAuthentication -DnsName *.contoso100.com, contoso100.com
8383
```
8484

8585
In the preceding sample, replace 'contoso100.com' with the DNS domain name of your managed domain. For example, if you created a managed domain called 'contoso100.onmicrosoft.com', replace 'contoso100.com' in the Subject attribute with 'contoso100.onmicrosoft.com' and '*.contoso100.com' in the DnsName attribute with '*.contoso100.onmicrosoft.com').

articles/active-directory-domain-services/active-directory-ds-getting-started-password-sync-synced-tenant.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ A synced Azure AD tenant is set to synchronize with your organization's on-premi
4646
### Install or update Azure AD Connect
4747
Install the latest recommended release of Azure AD Connect on a domain joined computer. If you have an existing instance of Azure AD Connect setup, you need to update it to use the latest version of Azure AD Connect. To avoid known issues/bugs that may have already been fixed, always use the latest version of Azure AD Connect.
4848

49-
**[Download Azure AD Connect](http://www.microsoft.com/download/details.aspx?id=47594)**
49+
**[Download Azure AD Connect](https://www.microsoft.com/download/details.aspx?id=47594)**
5050

5151
Recommended version: **1.1.614.0** - published on September 5, 2017.
5252

0 commit comments

Comments
 (0)