Skip to content

Commit 931c55a

Browse files
committed
[BULK] Fix code block formatting issues
1 parent 0e55530 commit 931c55a

File tree

7 files changed

+12
-15
lines changed

7 files changed

+12
-15
lines changed

articles/active-directory-b2c/configure-authentication-in-azure-static-app.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -136,11 +136,10 @@ Once you've added the app ID and secrete, use the following steps to add the Azu
136136
const { clientPrincipal } = payload;
137137
return clientPrincipal;
138138
}
139-
139+
140140
await getUserInfo();
141141
```
142142

143-
144143
> [!TIP]
145144
> If you can't run the above JavaScript code in your browser, navigate to the following URL `https://<app-name>.azurewebsites.net/.auth/me`. Replace the `<app-name>` with your Azure Web App.
146145

articles/active-directory-b2c/custom-email-sendgrid.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ With a SendGrid account created and SendGrid API key stored in an Azure AD B2C p
6666
1. Select **Blank Template** and then **Code Editor**.
6767
1. In the HTML editor, paste following HTML template or use your own. The `{{otp}}` and `{{email}}` parameters will be replaced dynamically with the one-time password value and the user email address.
6868

69-
```HTML
69+
```html
7070
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
7171

7272
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en"><head id="Head1">
@@ -154,17 +154,16 @@ With a SendGrid account created and SendGrid API key stored in an Azure AD B2C p
154154
<td valign="top" width="50%"></td>
155155
</tr>
156156
</table>
157-
</body>
157+
</body>
158158
</html>
159159
```
160160

161-
1. Expand **Settings** on the left, and for **Version Name**, enter a template version.
161+
1. Expand **Settings** on the left, and for **Version Name**, enter a template version.
162162
1. For **Subject**, enter `{{subject}}`.
163163
1. A the top of the page, select **Save**.
164164
1. Return to the **Transactional Templates** page by selecting the back arrow.
165165
1. Record the **ID** of template you created for use in a later step. For example, `d-989077fbba9746e89f3f6411f596fb96`. You specify this ID when you [add the claims transformation](#add-the-claims-transformation).
166166

167-
168167
[!INCLUDE [active-directory-b2c-important-for-custom-email-provider](../../includes/active-directory-b2c-important-for-custom-email-provider.md)]
169168

170169
## Add Azure AD B2C claim types

articles/active-directory-b2c/partner-biocatch.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -341,7 +341,7 @@ document.getElementById("clientSessionId").style.display = 'none';
341341

342342
</TechnicalProfile>
343343

344-
</RelyingParty>
344+
</RelyingParty>
345345
```
346346

347347
## Integrate with Azure AD B2C

articles/active-directory-b2c/partner-datawiza.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -77,9 +77,9 @@ To integrate your legacy on-premises app with Azure AD B2C, contact [Datawiza](h
7777
## Run DAB with a header-based application
7878

7979
1. You can use either Docker or Kubernetes to run DAB. The docker image is needed for users to create a sample header-based application. See instructions on how to [configure DAB and SSO integration](https://docs.datawiza.com/step-by-step/step3.html) for more details and how to [deploy DAB with Kubernetes](https://docs.datawiza.com/tutorial/web-app-AKS.html) for Kubernetes-specific instructions. A sample docker image `docker-compose.yml file` is provided for you to download and use. Log in to the container registry to download the images of DAB and the header-based application. Follow [these instructions](https://docs.datawiza.com/step-by-step/step3.html#important-step).
80-
81-
```yaml
82-
version: '3'
80+
81+
```yaml
82+
version: '3'
8383

8484
services:
8585
datawiza-access-broker:
@@ -102,7 +102,7 @@ To integrate your legacy on-premises app with Azure AD B2C, contact [Datawiza](h
102102
- "3001:3001"
103103
```
104104
105-
2. After executing `docker-compose -f docker-compose.yml up`, the header-based application should have SSO enabled with Azure AD B2C. Open a browser and type in `http://localhost:9772/`.
105+
2. After executing `docker-compose -f docker-compose.yml up`, the header-based application should have SSO enabled with Azure AD B2C. Open a browser and type in `http://localhost:9772/`.
106106

107107
3. An Azure AD B2C login page will show up.
108108

articles/active-directory-b2c/partner-xid.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -237,7 +237,7 @@ Now that you have a user journey add the new identity provider to the user journ
237237

238238
The following XML demonstrates the orchestration steps of a user journey with xID identity provider:
239239

240-
```xml
240+
```xml
241241

242242
<UserJourney Id="CombinedSignInAndSignUp">
243243
<OrchestrationSteps>

articles/active-directory/app-provisioning/application-provisioning-config-problem-scim-compatibility.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Below are sample requests to help outline what the sync engine currently sends v
7373
"value": "False"
7474
}
7575
]
76-
}
76+
}
7777
```
7878

7979
**With feature flag**
@@ -89,7 +89,7 @@ Below are sample requests to help outline what the sync engine currently sends v
8989
"value": false
9090
}
9191
]
92-
}
92+
}
9393
```
9494

9595
**Requests made to add a single-value string attribute:**

articles/active-directory/app-proxy/application-proxy-configure-complex-application.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,6 @@ If successful, this method returns a `204 No Content` response code and does not
6767
##### Request
6868
Here is an example of the request.
6969

70-
7170
```http
7271
PATCH https://graph.microsoft.com/beta/applications/{<object-id-of--the-complex-app-under-APP-Registrations}
7372
Content-type: application/json

0 commit comments

Comments
 (0)