Skip to content

Commit 6e522c7

Browse files
committed
2 parents 7abfb98 + 0aa44f9 commit 6e522c7

File tree

148 files changed

+1817
-1213
lines changed

Some content is hidden

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

148 files changed

+1817
-1213
lines changed

.openpublishing.publish.config.json

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -151,8 +151,37 @@
151151
"url": "https://github.com/Azure-Samples/functions-python-tensorflow-tutorial",
152152
"branch": "master",
153153
"branch_mapping": {}
154+
},
155+
{
156+
"path_to_root": "functions-quickstart-templates",
157+
"url": "https://github.com/Azure/azure-functions-templates",
158+
"branch": "dev"
159+
},
160+
{
161+
"path_to_root": "functions-docs-csharp",
162+
"url": "https://github.com/Azure-Samples/functions-docs-csharp",
163+
"branch": "master"
154164
},
155165
{
166+
"path_to_root": "functions-docs-javascript",
167+
"url": "https://github.com/Azure-Samples/functions-docs-javascript",
168+
"branch": "master"
169+
},
170+
{
171+
"path_to_root": "functions-docs-typescript",
172+
"url": "https://github.com/Azure-Samples/functions-docs-typescript",
173+
"branch": "master"
174+
},
175+
{
176+
"path_to_root": "functions-docs-python",
177+
"url": "https://github.com/Azure-Samples/functions-docs-python",
178+
"branch": "master"
179+
},
180+
{
181+
"path_to_root": "functions-docs-powershell",
182+
"url": "https://github.com/Azure-Samples/functions-docs-powershell",
183+
"branch": "master"
184+
}, {
156185
"path_to_root": "samples-personalizer",
157186
"url": "https://github.com/Azure-Samples/cognitive-services-personalizer-samples",
158187
"branch": "master"

.openpublishing.redirection.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7258,6 +7258,26 @@
72587258
"redirect_url": "/azure/azure-functions/functions-create-first-azure-function-azure-cli",
72597259
"redirect_document_id": false
72607260
},
7261+
{
7262+
"source_path": "articles/azure-functions/functions-create-first-function-python.md",
7263+
"redirect_url": "/azure/azure-functions/functions-create-first-azure-function-azure-cli?pivots=programming-language-python",
7264+
"redirect_document_id": false
7265+
},
7266+
{
7267+
"source_path": "articles/azure-functions/functions-create-first-function-powershell.md",
7268+
"redirect_url": "/azure/azure-functions/functions-create-first-function-vs-code?pivots=programming-language-powershell",
7269+
"redirect_document_id": false
7270+
},
7271+
{
7272+
"source_path": "articles/azure-functions/functions-create-first-azure-function-azure-cli-linux.md",
7273+
"redirect_url": "/azure/azure-functions/functions-create-first-azure-function-azure-cli?pivots=programming-language-python",
7274+
"redirect_document_id": false
7275+
},
7276+
{
7277+
"source_path": "articles/azure-functions/functions-add-output-binding-storage-queue-python.md",
7278+
"redirect_url": "/azure/azure-functions/functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-python",
7279+
"redirect_document_id": false
7280+
},
72617281
{
72627282
"source_path": "articles/azure-functions/create-visual-studio.md",
72637283
"redirect_url": "/azure/azure-functions/functions-create-your-first-function-visual-studio",

articles/active-directory-b2c/connect-with-saml-service-providers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ If you don't yet have a SAML service provider and an associated metadata endpoin
5959

6060
## 1. Set up certificates
6161

62-
To build a trust relationship between your service provider and Azure AD B2C, you need to provide X509 certificates and their private keys.
62+
To build a trust relationship between your service provider and Azure AD B2C, you need to provide the web app X509 certificates.
6363

6464
* **Service provider certificates**
6565
* Certificate with a private key stored in your Web App. This certificate is used by your service provider to sign the SAML request sent to Azure AD B2C. Azure AD B2C reads the public key from the service provider metadata to validate the signature.

articles/active-directory/azuread-dev/howto-v1-enable-sso-android.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ If a compatible broker is installed on the device, like the Microsoft Authentica
5656

5757
#### How Microsoft ensures the application is valid
5858

59-
The need to ensure the identity of an application call the broker is crucial to the security provided in broker assisted logins. iOS and Android do not enforce unique identifiers that are valid only for a given application, so malicious applications may "spoof" a legitimate application's identifier and receive the tokens meant for the legitimate application. To ensure Microsoft is always communicating with the right application at runtime, the developer is asked to provide a custom redirectURI when registering their application with Microsoft. **How developers should craft this redirect URI is discussed in detail below.** This custom redirectURI contains the certificate thumbprint of the application and is ensured to be unique to the application by the Google Play Store. When an application calls the broker, the broker asks the Android operating system to provide it with the certificate thumbprint that called the broker. The broker provides this certificate thumbprint to Microsoft in the call to the identity system. If the certificate thumbprint of the application does not match the certificate thumbprint provided to us by the developer during registration, access is denied to the tokens for the resource the application is requesting. This check ensures that only the application registered by the developer receives tokens.
59+
The need to ensure the identity of an application calling the broker is crucial to the security provided in broker assisted logins. iOS and Android do not enforce unique identifiers that are valid only for a given application, so malicious applications may "spoof" a legitimate application's identifier and receive the tokens meant for the legitimate application. To ensure Microsoft is always communicating with the right application at runtime, the developer is asked to provide a custom redirectURI when registering their application with Microsoft. **How developers should craft this redirect URI is discussed in detail below.** This custom redirectURI contains the certificate thumbprint of the application and is ensured to be unique to the application by the Google Play Store. When an application calls the broker, the broker asks the Android operating system to provide it with the certificate thumbprint that called the broker. The broker provides this certificate thumbprint to Microsoft in the call to the identity system. If the certificate thumbprint of the application does not match the certificate thumbprint provided to us by the developer during registration, access is denied to the tokens for the resource the application is requesting. This check ensures that only the application registered by the developer receives tokens.
6060

6161
Brokered-SSO logins have the following benefits:
6262

articles/active-directory/azuread-dev/howto-v1-enable-sso-ios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ If a compatible broker is installed on the device, like the Microsoft Authentica
104104

105105
#### How we ensure the application is valid
106106

107-
The need to ensure the identity of an application call the broker is crucial to the security we provide in broker assisted logins. Neither iOS nor Android enforces unique identifiers that are valid only for a given application, so malicious applications may "spoof" a legitimate application's identifier and receive the tokens meant for the legitimate application. To ensure we are always communicating with the right application at runtime, we ask the developer to provide a custom redirectURI when registering their application with Microsoft. How developers should craft this redirect URI is discussed in detail below. This custom redirectURI contains the Bundle ID of the application and is ensured to be unique to the application by the Apple App Store. When an application calls the broker, the broker asks the iOS operating system to provide it with the Bundle ID that called the broker. The broker provides this Bundle ID to Microsoft in the call to our identity system. If the Bundle ID of the application does not match the Bundle ID provided to us by the developer during registration, we will deny access to the tokens for the resource the application is requesting. This check ensures that only the application registered by the developer receives tokens.
107+
The need to ensure the identity of an application that calls the broker is crucial to the security we provide in broker assisted logins. Neither iOS nor Android enforces unique identifiers that are valid only for a given application, so malicious applications may "spoof" a legitimate application's identifier and receive the tokens meant for the legitimate application. To ensure we are always communicating with the right application at runtime, we ask the developer to provide a custom redirectURI when registering their application with Microsoft. How developers should craft this redirect URI is discussed in detail below. This custom redirectURI contains the Bundle ID of the application and is ensured to be unique to the application by the Apple App Store. When an application calls the broker, the broker asks the iOS operating system to provide it with the Bundle ID that called the broker. The broker provides this Bundle ID to Microsoft in the call to our identity system. If the Bundle ID of the application does not match the Bundle ID provided to us by the developer during registration, we will deny access to the tokens for the resource the application is requesting. This check ensures that only the application registered by the developer receives tokens.
108108

109109
**The developer has the choice whether the SDK calls the broker or uses the non-broker assisted flow.** However if the developer chooses not to use the broker-assisted flow they lose the benefit of using SSO credentials that the user may have already added on the device and prevents their application from being used with business features Microsoft provides its customers such as Conditional Access, Intune management capabilities, and certificate-based authentication.
110110

articles/active-directory/develop/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -405,6 +405,8 @@
405405
href: v2-admin-consent.md
406406
- name: Application consent experiences
407407
href: application-consent-experience.md
408+
- name: Conditional access
409+
href: v2-conditional-access-dev-guide.md
408410
- name: National Clouds
409411
items:
410412
- name: Overview
Loading
Loading
29.8 KB
Loading
17.5 KB
Loading

0 commit comments

Comments
 (0)