Skip to content

Commit ca382fa

Browse files
authored
Merge pull request #188230 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents c8adecd + 5997e57 commit ca382fa

File tree

6 files changed

+7
-7
lines changed

6 files changed

+7
-7
lines changed

articles/active-directory/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Scoping filters are configured as part of the attribute mappings for each Azure
8282

8383
f. **IS NOT NULL**. Clause returns "true" if the evaluated attribute isn't empty.
8484

85-
g. **REGEX MATCH**. Clause returns "true" if the evaluated attribute matches a regular expression pattern. For example: ([1-9][0-9]) matches any number between 10 and 99.
85+
g. **REGEX MATCH**. Clause returns "true" if the evaluated attribute matches a regular expression pattern. For example: ([1-9][0-9]) matches any number between 10 and 99 (case sensitive).
8686

8787
h. **NOT REGEX MATCH**. Clause returns "true" if the evaluated attribute doesn't match a regular expression pattern.
8888

articles/active-directory/fundamentals/multi-tenant-user-management-scenarios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ There are many ways end users can get invited to access resource tenant resource
2727

2828
* [Application-based invitations](../external-identities/o365-external-user.md). Microsoft applications may enable invitation of guest users. B2B invitation settings must be configured both in Azure AD B2B and in the relevant application or applications.
2929

30-
* [MyApps]../user-help/my-apps-portal-end-user-access). Users invite and assign a guest user to an application using MyApps. The user account must have [application self-service sign up](../manage-apps/manage-self-service-access.md) approver permissions. They can invite guest users to a group if they're a group owner.
30+
* [MyApps](../manage-apps/my-apps-deployment-plan.md). Users invite and assign a guest user to an application using MyApps. The user account must have [application self-service sign up](../manage-apps/manage-self-service-access.md) approver permissions. They can invite guest users to a group if they're a group owner.
3131

3232
* [Entitlement Management](../governance/entitlement-management-overview.md): Enables admins or resource owners to tie resources, allowed external organizations, guest user expiration, and access policies together in access packages. Access packages can be published to enable self-service sign-up for resource access by guest users.
3333

articles/api-management/virtual-network-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ When an API Management service instance is hosted in a VNet, the ports in the fo
3838
| * / 443 | Outbound | TCP | VirtualNetwork / AzureActiveDirectory | [Azure Active Directory](api-management-howto-aad.md) and Azure Key Vault dependency (optional) | External & Internal |
3939
| * / 1433 | Outbound | TCP | VirtualNetwork / SQL | **Access to Azure SQL endpoints** | External & Internal |
4040
| * / 443 | Outbound | TCP | VirtualNetwork / AzureKeyVault | **Access to Azure Key Vault** | External & Internal |
41-
| * / 5671, 5672, 443 | Outbound | TCP | VirtualNetwork / Azure Event Hubs | Dependency for [Log to Azure Event Hubs policy](api-management-howto-log-event-hubs.md) and monitoring agent (optional) | External & Internal |
41+
| * / 5671, 5672, 443 | Outbound | TCP | VirtualNetwork / EventHub | Dependency for [Log to Azure Event Hubs policy](api-management-howto-log-event-hubs.md) and monitoring agent (optional) | External & Internal |
4242
| * / 445 | Outbound | TCP | VirtualNetwork / Storage | Dependency on Azure File Share for [GIT](api-management-configuration-repository-git.md) (optional) | External & Internal |
4343
| * / 443, 12000 | Outbound | TCP | VirtualNetwork / AzureCloud | Health and Monitoring Extension (optional) | External & Internal |
4444
| * / 1886, 443 | Outbound | TCP | VirtualNetwork / AzureMonitor | Publish [Diagnostics Logs and Metrics](api-management-howto-use-azure-monitor.md), [Resource Health](../service-health/resource-health-overview.md), and [Application Insights](api-management-howto-app-insights.md) (optional) | External & Internal |

articles/azure-monitor/app/ilogger.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ By default, ASP.NET Core applications have an Application Insights logging provi
3636

3737
```xml
3838
<ItemGroup>
39-
<PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.17.0" />
39+
<PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.19.0" />
4040
</ItemGroup>
4141
```
4242

articles/container-registry/manual-regional-move.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ az group create --name myResourceGroup --location eastus
8888
Use the [az deployment group create](/cli/azure/deployment/group#az_deployment_group_create) command to deploy the target registry, using the template:
8989

9090
```azurecli
91-
az deployment group --resource-group myResourceGroup \
91+
az deployment group create --resource-group myResourceGroup \
9292
--template-file template.json --name mydeployment
9393
```
9494

@@ -149,4 +149,4 @@ After you have successfully deployed the target registry, migrated content, and
149149
## Next steps
150150

151151
* Learn more about [importing container images](container-registry-import-images.md) to an Azure container registry from a public registry or another private registry.
152-
* See the [Resource Manager template reference](/azure/templates/microsoft.containerregistry/registries) for Azure Container Registry.
152+
* See the [Resource Manager template reference](/azure/templates/microsoft.containerregistry/registries) for Azure Container Registry.

articles/virtual-machines/windows/run-command-managed.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ az vm run-command delete --name "myRunCommand" --vm-name "myVM" --resource-group
7676
This command will deliver the script to the VM, execute it, and return the captured output.
7777

7878
```powershell-interactive
79-
Set-AzVMRunCommand -ResourceGroupName "myRG" -VMName "myVM" -Name "RunCommandName" – Script "Write-Host Hello World!"
79+
Set-AzVMRunCommand -ResourceGroupName "myRG" -VMName "myVM" -Name "RunCommandName" –SourceScript "Write-Host Hello World!"
8080
```
8181

8282
### List all deployed RunCommand resources on a VM

0 commit comments

Comments
 (0)