Skip to content

Commit 7fe06a9

Browse files
stevenmatthewstevenmatthew
committed
Fixed broken URL
2 parents 35f21c6 + 1e7e0ea commit 7fe06a9

File tree

267 files changed

+3001
-2139
lines changed

Some content is hidden

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

267 files changed

+3001
-2139
lines changed

‎.openpublishing.redirection.json

Lines changed: 21 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -115,84 +115,89 @@
115115
"redirect_url": "/azure/migrate/discover-and-assess-using-private-endpoints",
116116
"redirect_document_id": false
117117
},
118+
{
119+
"source_path": "articles/operator-5g-core/index.yml",
120+
"redirect_url": "https://learn.microsoft.com",
121+
"redirect_document_id": false
122+
},
118123
{
119124
"source_path": "articles/operator-5g-core/concept-centralized-lifecycle-management.md",
120-
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-centralized-lifecycle-management",
125+
"redirect_url": "https://learn.microsoft.com",
121126
"redirect_document_id": false
122127
},
123128
{
124129
"source_path": "articles/operator-5g-core/concept-deployment-order.md",
125-
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-deployment-order",
130+
"redirect_url": "https://learn.microsoft.com",
126131
"redirect_document_id": false
127132
},
128133
{
129134
"source_path": "articles/operator-5g-core/concept-observability-analytics.md",
130-
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-observability-analytics",
135+
"redirect_url": "https://learn.microsoft.com",
131136
"redirect_document_id": false
132137
},
133138
{
134139
"source_path": "articles/operator-5g-core/concept-security.md",
135-
"redirect_url": "/previous-versions/azure/operator-5g-core/concept-security",
140+
"redirect_url": "https://learn.microsoft.com",
136141
"redirect_document_id": false
137142
},
138143
{
139144
"source_path": "articles/operator-5g-core/how-to-configure-network-function.md",
140-
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-configure-network-function",
145+
"redirect_url": "https://learn.microsoft.com",
141146
"redirect_document_id": false
142147
},
143148
{
144149
"source_path": "articles/operator-5g-core/how-to-delete-network-function-cluster.md",
145-
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-delete-network-function-cluster",
150+
"redirect_url": "https://learn.microsoft.com",
146151
"redirect_document_id": false
147152
},
148153
{
149154
"source_path": "articles/operator-5g-core/how-to-deploy-network-functions.md",
150-
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-deploy-network-functions",
155+
"redirect_url": "https://learn.microsoft.com",
151156
"redirect_document_id": false
152157
},
153158
{
154159
"source_path": "articles/operator-5g-core/how-to-deploy-observability.md",
155-
"redirect_url": "/previous-versions/azure/operator-5g-core/how-to-deploy-observability",
160+
"redirect_url": "https://learn.microsoft.com",
156161
"redirect_document_id": false
157162
},
158163
{
159164
"source_path": "articles/operator-5g-core/overview-product.md",
160-
"redirect_url": "/previous-versions/azure/operator-5g-core/overview-product",
165+
"redirect_url": "https://learn.microsoft.com",
161166
"redirect_document_id": false
162167
},
163168
{
164169
"source_path": "articles/operator-5g-core/quickstart-complete-prerequisites-deploy-azure-kubernetes-service.md",
165-
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-azure-kubernetes-service",
170+
"redirect_url": "https://learn.microsoft.com",
166171
"redirect_document_id": false
167172
},
168173
{
169174
"source_path": "articles/operator-5g-core/quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service.md",
170-
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service",
175+
"redirect_url": "https://learn.microsoft.com",
171176
"redirect_document_id": false
172177
},
173178
{
174179
"source_path": "articles/operator-5g-core/quickstart-configure-extension-for-status-monitoring.md",
175-
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-configure-extension-for-status-monitoring",
180+
"redirect_url": "https://learn.microsoft.com",
176181
"redirect_document_id": false
177182
},
178183
{
179184
"source_path": "articles/operator-5g-core/quickstart-deploy-5g-core.md",
180-
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-deploy-5g-core",
185+
"redirect_url": "https://learn.microsoft.com",
181186
"redirect_document_id": false
182187
},
183188
{
184189
"source_path": "articles/operator-5g-core/quickstart-monitor-deployment-status.md",
185-
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-monitor-deployment-status",
190+
"redirect_url": "https://learn.microsoft.com",
186191
"redirect_document_id": false
187192
},
188193
{
189194
"source_path": "articles/operator-5g-core/quickstart-subscription.md",
190-
"redirect_url": "/previous-versions/azure/operator-5g-core/quickstart-subscription",
195+
"redirect_url": "https://learn.microsoft.com",
191196
"redirect_document_id": false
192197
},
193198
{
194199
"source_path": "articles/operator-5g-core/tutorial-configure-network-function.md",
195-
"redirect_url": "/previous-versions/azure/operator-5g-core/tutorial-configure-network-function",
200+
"redirect_url": "https://learn.microsoft.com",
196201
"redirect_document_id": false
197202
},
198203
{

‎articles/active-directory-b2c/api-connectors-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -244,7 +244,7 @@ If you reference a REST API technical profile directly from a user journey, the
244244

245245
## Development of your REST API
246246

247-
Your REST API can be developed on any platform and written in any programing language, as long as it's secure and can send and receive claims in JSON format.
247+
Your REST API can be developed on any platform and written in any programming language, as long as it's secure and can send and receive claims in JSON format.
248248

249249
The request to your REST API service comes from Azure AD B2C servers. The REST API service must be published to a publicly accessible HTTPS endpoint. The REST API call arrives from an Azure data center IP address.
250250

‎articles/active-directory-b2c/claimsschema.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -325,7 +325,7 @@ The **DateTimeDropdown** user input type is used to provide a set of drop-downs
325325

326326
The **RadioSingleSelect** user input type is used to provide a collection of radio buttons that allows the user to select one option.
327327

328-
![Using claim type with radiodsingleselect](./media/claimsschema/radiosingleselect.png)
328+
![Using claim type with radiosingleselect](./media/claimsschema/radiosingleselect.png)
329329

330330
```xml
331331
<ClaimType Id="color">

‎articles/active-directory-b2c/configure-authentication-sample-angular-spa-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -190,7 +190,7 @@ Your final configuration file should look like the following JSON:
190190
```json
191191
{
192192
"credentials": {
193-
"tenantName": "<your-tenant-namee>",
193+
"tenantName": "<your-tenant-name>",
194194
"clientID": "<your-webapi-application-ID>",
195195
"issuer": "https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/"
196196
},

‎articles/active-directory-b2c/custom-policy-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ In the [Azure AD B2C samples GitHub repository](https://github.com/azure-ad-b2c/
4141

4242
### Claims
4343

44-
A claim provides temporary storage of data during an Azure AD B2C policy execution. Claims are more like variable in a programing language. It can store information about the user, such as first name, last name, or any other claim obtained from the user or other systems (claims exchanges). The [claims schema](claimsschema.md) is the place where you declare your claims.
44+
A claim provides temporary storage of data during an Azure AD B2C policy execution. Claims are more like variable in a programming language. It can store information about the user, such as first name, last name, or any other claim obtained from the user or other systems (claims exchanges). The [claims schema](claimsschema.md) is the place where you declare your claims.
4545

4646
When the policy runs, Azure AD B2C sends and receives claims to and from internal and external parties and then sends a subset of these claims to your relying party application as part of the token. Claims are used in these ways:
4747

‎articles/active-directory-b2c/custom-policy-reference-sso.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ To use a session provider in your technical profile:
7171

7272
```xml
7373
<TechnicalProfile Id="SM-AAD">
74-
<DisplayName>Session Mananagement Provider</DisplayName>
74+
<DisplayName>Session Management Provider</DisplayName>
7575
<Protocol Name="Proprietary" Handler="Web.TPEngine.SSO.DefaultSSOSessionProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
7676
<PersistedClaims>
7777
<PersistedClaim ClaimTypeReferenceId="objectId" />

‎articles/active-directory-b2c/json-transformations.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Create a JSON single element array from a claim value. Check out the [Live demo]
3636
The following example creates a JSON single array.
3737

3838
```xml
39-
<ClaimsTransformation Id="createlJsonPayload" TransformationMethod="CreateJsonArray">
39+
<ClaimsTransformation Id="CreateJsonPayload" TransformationMethod="CreateJsonArray">
4040
<InputClaims>
4141
<InputClaim ClaimTypeReferenceId="email" TransformationClaimType="inputClaim" />
4242
</InputClaims>
@@ -315,7 +315,7 @@ In the following example, the claims transformation extracted the `emailAddress`
315315
The GetClaimFromJson claims transformation gets a single element from a JSON data. In the preceding example, the emailAddress. To get the displayName, create another claims transformation. For example:
316316

317317
```xml
318-
<ClaimsTransformation Id="GetDispalyNameClaimFromJson" TransformationMethod="GetClaimFromJson">
318+
<ClaimsTransformation Id="GetDisplayNameClaimFromJson" TransformationMethod="GetClaimFromJson">
319319
<InputClaims>
320320
<InputClaim ClaimTypeReferenceId="customUserData" TransformationClaimType="inputJson" />
321321
</InputClaims>
@@ -593,7 +593,7 @@ In the following example, the claims transformation extracts the first element (
593593

594594
- Output claims:
595595
- **key**: givenName
596-
- **value**: Emilty
596+
- **value**: Emily
597597

598598

599599
## GetSingleValueFromJsonArray
@@ -637,7 +637,7 @@ Convert XML data to JSON format. Check out the [Live demo](https://github.com/az
637637
```xml
638638
<ClaimsTransformation Id="ConvertXmlToJson" TransformationMethod="XmlStringToJsonString">
639639
<InputClaims>
640-
<InputClaim ClaimTypeReferenceId="intpuXML" TransformationClaimType="xml" />
640+
<InputClaim ClaimTypeReferenceId="inputXML" TransformationClaimType="xml" />
641641
</InputClaims>
642642
<OutputClaims>
643643
<OutputClaim ClaimTypeReferenceId="outputJson" TransformationClaimType="json" />

‎articles/active-directory-b2c/jwt-issuer-technical-profile.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ The following example shows a technical profile for `JwtIssuer`:
5050

5151
## Input, output, and persist claims
5252

53-
The **InputClaims**, **OutputClaims**, and **PersistClaims** elements are empty or absent. The **InutputClaimsTransformations** and **OutputClaimsTransformations** elements are also absent.
53+
The **InputClaims**, **OutputClaims**, and **PersistClaims** elements are empty or absent. The **InputClaimsTransformations** and **OutputClaimsTransformations** elements are also absent.
5454

5555
## Metadata
5656

‎articles/active-directory-b2c/localization.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ The ElementType reference to a claim type, a claim transformation, or a user int
161161
| Identity provider name |`ClaimsProvider`| | The ID of the ClaimsExchange element|
162162
| Claim type attributes|`ClaimType`|Name of the claim type| The attribute of the claim to be localized. Possible values: `AdminHelpText`, `DisplayName`, `PatternHelpText`, and `UserHelpText`.|
163163
|Error message|`ErrorMessage`||The ID of the error message |
164-
|Copies localized strings into claims|`GetLocalizedStringsTra nsformationClaimType`||The name of the output claim|
164+
|Copies localized strings into claims|`GetLocalizedStringsTransformationClaimType`||The name of the output claim|
165165
|Predicate user message|`Predicate`|The name of the predicate| The attribute of the predicate to be localized. Possible values: `HelpText`.|
166166
|Predicate group user message|`PredicateValidation`|The ID of the PredicateValidation element.|The ID of the PredicateGroup element. The predicate group must be a child of the predicate validation element as defined in the ElementId.|
167167
|User interface elements |`UxElement` | | The ID of the user interface element to be localized.|
@@ -246,7 +246,7 @@ The FormatLocalizedStringTransformationClaimType value is used to format claims
246246
<InputClaim ClaimTypeReferenceId="email" />
247247
</InputClaims>
248248
<InputParameters>
249-
<InputParameter Id="stringFormatId" DataType="string" Value="ResponseMessge_EmailExists" />
249+
<InputParameter Id="stringFormatId" DataType="string" Value="ResponseMessage_EmailExists" />
250250
</InputParameters>
251251
<OutputClaims>
252252
<OutputClaim ClaimTypeReferenceId="responseMsg" TransformationClaimType="outputClaim" />
@@ -257,7 +257,7 @@ The FormatLocalizedStringTransformationClaimType value is used to format claims
257257
The following example shows how to localize string format of the FormatLocalizedStringTransformationClaimType claims transformation.
258258

259259
```xml
260-
<LocalizedString ElementType="FormatLocalizedStringTransformationClaimType" StringId="ResponseMessge_EmailExists">The email '{0}' is already an account in this organization. Click Next to sign in with that account.</LocalizedString>
260+
<LocalizedString ElementType="FormatLocalizedStringTransformationClaimType" StringId="ResponseMessage_EmailExists">The email '{0}' is already an account in this organization. Click Next to sign in with that account.</LocalizedString>
261261
```
262262

263263
### GetLocalizedStringsTransformationClaimType

‎articles/active-directory-b2c/partner-dynamics-365-fraud-protection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ In the provided [custom policies](https://github.com/azure-ad-b2c/partner-integr
117117
|{Settings:ContentDefinitionBaseUri}|Endpoint in where you deployed the UI files|`https://<my-storage-account>.blob.core.windows.net/<my-storage-container>`|
118118
|{Settings:DfpApiBaseUrl}|The base path for your DFP API instance, found in the DFP portal| `https://tenantname-00001111-aaaa-2222-bbbb-3333cccc4444.api.dfp.dynamics.com/v1.0/`|
119119
|{Settings:DfpApiAuthScope}|The client_credentials scope for the DFP API service|`https://api.dfp.dynamics-int.com/.default or https://api.dfp.dynamics.com/.default`|
120-
|{Settings:DfpTenantId}|The ID of the Microsoft Entra tenant (not B2C) where DFP is licensed and installed|`00001111-aaaa-2222-bbbb-3333cccc4444` or `consoto.onmicrosoft.com` |
120+
|{Settings:DfpTenantId}|The ID of the Microsoft Entra tenant (not B2C) where DFP is licensed and installed|`00001111-aaaa-2222-bbbb-3333cccc4444` or `contoso.onmicrosoft.com` |
121121
|{Settings:DfpAppClientIdKeyContainer}|Name of the policy key-in which you save the DFP client ID|`B2C_1A_DFPClientId`|
122122
|{Settings:DfpAppClientSecretKeyContainer}|Name of the policy key-in which you save the DFP client secret |`B2C_1A_DFPClientSecret`|
123123
|{Settings:DfpEnvironment}| The ID of the DFP environment.|Environment ID is a global unique identifier of the DFP environment that you send the data to. Your custom policy should call the API endpoint, including the query string parameter `x-ms-dfpenvid=your-env-id>`|

0 commit comments

Comments
 (0)