Skip to content

Commit ae3d707

Browse files
authored
Merge pull request #110884 from MicrosoftDocs/master
4/09 PM Publish
2 parents 2549046 + b14e5a1 commit ae3d707

File tree

122 files changed

+1033
-1016
lines changed

Some content is hidden

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

122 files changed

+1033
-1016
lines changed

.openpublishing.redirection.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -50679,11 +50679,6 @@
5067950679
"redirect_url": "/azure/developer/chef/overview",
5068050680
"redirect_document_id": false
5068150681
},
50682-
{
50683-
"source_path": "articles/chef/",
50684-
"redirect_url": "/azure/developer/chef/",
50685-
"redirect_document_id": false
50686-
},
5068750682
{
5068850683
"source_path": "articles/chef/index.yml",
5068950684
"redirect_url": "/azure/developer/chef/",

articles/active-directory/develop/msal-js-initializing-client-applications.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Before initializing an application, you first need to [register it with the Azur
3232

3333
You can use MSAL.js as follows in a plain JavaScript/Typescript application. Initialize MSAL authentication context by instantiating `UserAgentApplication` with a configuration object. The minimum required config to initialize MSAL.js is the clientID of your application which you should get from the application registration portal.
3434

35-
For authentication methods with redirect flows (`loginRedirect` and `acquireTokenRedirect`), you will need to explicitly register a callback for success or error through `handleRedirectCallback()` method. This is needed since redirect flows do not return promises as the methods with a pop-up experience do.
35+
For authentication methods with redirect flows (`loginRedirect` and `acquireTokenRedirect`), in MSAL.js 1.2.x or earlier, you will need to explicitly register a callback for success or error through `handleRedirectCallback()` method. This is needed since redirect flows do not return promises as the methods with a pop-up experience do. This became optional in MSAL.js version 1.3.0.
3636

3737
```javascript
3838
// Configuration object constructed

articles/app-service/app-service-web-get-started-php.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,12 +67,16 @@ In the Cloud Shell, create a web app in the `myAppServicePlan` App Service plan
6767

6868
In the following example, replace `<app_name>` with a globally unique app name (valid characters are `a-z`, `0-9`, and `-`). The runtime is set to `PHP|7.0`. To see all supported runtimes, run [`az webapp list-runtimes`](/cli/azure/webapp?view=azure-cli-latest#az-webapp-list-runtimes).
6969

70+
7071
```azurecli-interactive
7172
# Bash
7273
az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name <app_name> --runtime "PHP|7.0" --deployment-local-git
7374
# PowerShell
7475
az --% webapp create --resource-group myResourceGroup --plan myAppServicePlan --name <app_name> --runtime "PHP|7.0" --deployment-local-git
7576
```
77+
> [!NOTE]
78+
> The stop-parsing symbol `(--%)`, introduced in PowerShell 3.0, directs PowerShell to refrain from interpreting input as PowerShell commands or expressions.
79+
>
7680
7781
When the web app has been created, the Azure CLI shows output similar to the following example:
7882

articles/automation/TOC.yml

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -262,7 +262,7 @@
262262
href: /powershell/scripting/dsc/overview/overview
263263
- name: Quickstarts
264264
items:
265-
- name: Getting Started
265+
- name: Get Started
266266
href: automation-dsc-getting-started.md
267267
displayName: DSC
268268
- name: Manage the configuration of a machine
@@ -278,31 +278,28 @@
278278
- name: Configure servers to a desired state and manage drift with State Configuration
279279
href: tutorial-configure-servers-desired-state.md
280280
displayName: DSC, compliance
281-
- name: Onboarding machines for management
282-
href: automation-dsc-onboarding.md
283-
displayName: DSC, state configuration
284-
- name: Compiling DSC configurations
281+
- name: Compile DSC configurations
285282
href: automation-dsc-compile.md
286283
displayName: state configuration, composite resources, configurationData
287284
- name: Remediate non-compliant DSC servers
288285
href: automation-dsc-remediate.md
289286
displayName: state configuration, DSC, remediate
290-
- name: Composing DSC Configurations using Composite Resources
287+
- name: Compose DSC configurations using composite resources
291288
href: compose-configurationwithcompositeresources.md
292-
- name: Continuous deployment using Chocolatey
289+
- name: Provide continuous deployment using Chocolatey
293290
href: automation-dsc-cd-chocolatey.md
294291
displayName: dsc, state configuration
295292
- name: Forward State Configuration reporting data to Azure Monitor logs
296293
href: automation-dsc-diagnostics.md
297294
displayName: DSC
298295
- name: Troubleshoot
299296
items:
300-
- name: Onboarding
297+
- name: Troubleshoot onboarding
301298
href: troubleshoot/onboarding.md
302299
displayName: troubleshoot
303300
- name: Troubleshoot State Configuration (DSC)
304301
href: troubleshoot/desired-state-configuration.md
305-
displayName: Desired State Configuration, troubleshoot
302+
displayName: state configuration, DSC, troubleshoot
306303
- name: Reference
307304
items:
308305
- name: Community Solutions

0 commit comments

Comments
 (0)