Skip to content

Commit 510e995

Browse files
authored
Merge pull request #260030 from MicrosoftDocs/main
12/1/2023 AM Publish
2 parents d7ae827 + 1b3ace8 commit 510e995

File tree

117 files changed

+738
-748
lines changed

Some content is hidden

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

117 files changed

+738
-748
lines changed

articles/active-directory-b2c/best-practices.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,6 @@ Define your application and service architecture, inventory current systems, and
4141
| Migrate existing apps to b2clogin.com | The deprecation of login.microsoftonline.com will go into effect for all Azure AD B2C tenants on 04 December 2020. [Learn more](b2clogin.md). |
4242
| Use Identity Protection and Conditional Access | Use these capabilities for significantly greater control over risky authentications and access policies. Azure AD B2C Premium P2 is required. [Learn more](conditional-access-identity-protection-overview.md). |
4343
|Tenant size | You need to plan with Azure AD B2C tenant size in mind. By default, Azure AD B2C tenant can accommodate 1.25 million objects (user accounts and applications). You can increase this limit to 5.25 million objects by adding a custom domain to your tenant, and verifying it. If you need a bigger tenant size, you need to contact [Support](find-help-open-support-ticket.md).|
44-
| Use Identity Protection and Conditional Access | Use these capabilities for greater control over risky authentications and access policies. Azure AD B2C Premium P2 is required. [Learn more](conditional-access-identity-protection-overview.md). |
4544

4645
## Implementation
4746

articles/active-directory-b2c/whats-new-docs.md

Lines changed: 19 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory business-to-customer (B2C)"
33
description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
4-
ms.date: 11/01/2023
4+
ms.date: 12/01/2023
55
ms.service: active-directory
66
ms.subservice: B2C
77
ms.topic: reference
@@ -15,6 +15,24 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
1717

18+
## November 2023
19+
20+
### Updated articles
21+
22+
- [Set up a password reset flow in Azure Active Directory B2C](add-password-reset-policy.md) - Editorial updates
23+
- [Enrich tokens with claims from external sources using API connectors](add-api-connector-token-enrichment.md) - Editorial updates
24+
- [Enable custom domains for Azure Active Directory B2C](custom-domain.md) - Editorial updates
25+
- [Set up sign-in for multitenant Microsoft Entra ID using custom policies in Azure Active Directory B2C](identity-provider-azure-ad-multi-tenant.md) - Editorial updates
26+
- [Manage Azure AD B2C with Microsoft Graph](microsoft-graph-operations.md) - Editorial updates
27+
- [Enable multifactor authentication in Azure Active Directory B2C](multi-factor-authentication.md) - Editorial updates
28+
- [What is Azure Active Directory B2C?](overview.md) - Editorial updates
29+
- [Technical and feature overview of Azure Active Directory B2C](technical-overview.md) - Editorial updates
30+
- [Tutorial: Create user flows and custom policies in Azure Active Directory B2C](tutorial-create-user-flows.md) - Editorial updates
31+
- [User flows and custom policies overview](user-flow-overview.md) - Editorial updates
32+
- [OAuth 2.0 authorization code flow in Azure Active Directory B2C](authorization-code-flow.md) - Editorial updates
33+
- [Create and read a user account by using Azure Active Directory B2C custom policy](custom-policies-series-store-user.md) - Editorial updates
34+
- [Define a Microsoft Entra multifactor authentication technical profile in an Azure AD B2C custom policy](multi-factor-auth-technical-profile.md) - Editorial updates
35+
1836
## October 2023
1937

2038
### Updated articles
@@ -44,11 +62,4 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
4462
- [Set up a sign-up and sign-in flow with a social account by using Azure Active Directory B2C custom policy](custom-policies-series-sign-up-or-sign-in-federation.md) - Editorial updates
4563
- [Create and read a user account by using Azure Active Directory B2C custom policy](custom-policies-series-store-user.md) - Editorial updates
4664

47-
## August 2023
48-
49-
### Updated articles
50-
51-
- [Page layout versions](page-layout.md) - Editorial updates
52-
- [Secure your API used an API connector in Azure AD B2C](secure-rest-api.md) - Oauth Bearer Authentication updated to GA
53-
5465

articles/aks/azure-csi-disk-storage-provision.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -328,7 +328,7 @@ When you create an Azure disk for use with AKS, you can create the disk resource
328328
pvc-azuredisk Bound pv-azuredisk 20Gi RWO 5s
329329
```
330330

331-
5. Create a *azure-disk-pod.yaml* file to reference your *PersistentVolumeClaim*.
331+
5. Create an *azure-disk-pod.yaml* file to reference your *PersistentVolumeClaim*.
332332

333333
```yaml
334334
apiVersion: v1

articles/azure-arc/kubernetes/tutorial-use-gitops-flux2.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Tutorial: Deploy applications using GitOps with Flux v2"
33
description: "This tutorial shows how to use GitOps with Flux v2 to manage configuration and application deployment in Azure Arc and AKS clusters."
4-
ms.date: 10/18/2023
4+
ms.date: 12/01/2023
55
ms.topic: tutorial
66
ms.custom: template-tutorial, devx-track-azurecli, references_regions, ignite-2022
77
---
@@ -608,14 +608,13 @@ Starting with [`microsoft.flux` v1.8.0](extensions-release.md#flux-gitops), you
608608

609609
1. Be sure to provide proper permissions for workload identity for the resource that you want source-controller or image-reflector controller to pull. For example, if using Azure Container Registry, `AcrPull` permissions are required.
610610

611-
612611
## Delete the Flux configuration and extension
613612

614-
Use the following commands to delete your Flux configuration and, if desired, the Flux extension itself.
613+
Use the following commands to delete your Flux configurations and, if desired, the Flux extension itself.
615614

616615
### [Azure CLI](#tab/azure-cli)
617616

618-
#### Delete the Flux configuration
617+
#### Delete the Flux configurations
619618

620619
The following command deletes both the `fluxConfigurations` resource in Azure and the Flux configuration objects in the cluster. Because the Flux configuration was originally created with the `prune=true` parameter for the kustomization, all of the objects created in the cluster based on manifests in the Git repository will be removed when the Flux configuration is removed. However, this command doesn't remove the Flux extension itself.
621620

@@ -627,6 +626,9 @@ az k8s-configuration flux delete -g flux-demo-rg -c flux-demo-arc -n cluster-con
627626

628627
When you delete the Flux extension, both the `microsoft.flux` extension resource in Azure and the Flux extension objects in the cluster will be removed.
629628

629+
> [!IMPORTANT]
630+
> Be sure to delete all Flux configurations in the cluster before you delete the Flux extension. Deleting the extension without first deleting the Flux configurations may leave your cluster in an unstable condition.
631+
630632
If the Flux extension was created automatically when the Flux configuration was first created, the extension name will be `flux`.
631633

632634
```azurecli
@@ -648,6 +650,9 @@ When you delete a Flux configuration, all of the Flux configuration objects in t
648650

649651
When you delete the Flux extension, both the `microsoft.flux` extension resource in Azure and the Flux extension objects in the cluster will be removed.
650652

653+
> [!IMPORTANT]
654+
> Be sure to delete all Flux configurations in the cluster before you delete the Flux extension. Deleting the extension without first deleting the Flux configurations may leave your cluster in an unstable condition.
655+
651656
For an Azure Arc-enabled Kubernetes cluster, navigate to the cluster and select **Extensions**. Select the `flux` extension and select **Uninstall**, then confirm the deletion.
652657

653658
For AKS clusters, you can't use the Azure portal to delete the extension. Instead, use the following Azure CLI command:

articles/azure-arc/servers/manage-agent.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,7 @@ Links to the current and previous releases of the Windows agents are available b
8282
sudo zypper install -f azcmagent-1.28.02260-755
8383
```
8484

85+
8586
---
8687

8788
## Upgrade the agent
@@ -423,7 +424,7 @@ Proxy bypass value when set to `ArcData` only bypasses the traffic of the Azure
423424
| --------------------- | ------------------ |
424425
| `AAD` | `login.windows.net`</br>`login.microsoftonline.com`</br> `pas.windows.net` |
425426
| `ARM` | `management.azure.com` |
426-
| `Arc` | `his.arc.azure.com`</br>`guestconfiguration.azure.com`</br> `san-af-<location>-prod.azurewebsites.net`</br>`telemetry.<location>.arcdataservices.com`|
427+
| `Arc` | `his.arc.azure.com`</br>`guestconfiguration.azure.com` |
427428
| `ArcData` <sup>1</sup> | `san-af-<region>-prod.azurewebsites.net`</br>`telemetry.<location>.arcdataservices.com` |
428429

429430
<sup>1</sup> The proxy bypass value `ArcData` is available starting with Azure Connected Machine agent version 1.36 and Azure Extension for SQL Server version 1.1.2504.99. Earlier versions include the SQL Server enabled by Azure Arc endpoints in the "Arc" proxy bypass value.

articles/azure-arc/system-center-virtual-machine-manager/enable-guest-management-at-scale.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: PriskeyJeronika-MS
77
ms.author: v-gjeronika
88
manager: jsuri
99
ms.topic: how-to
10-
ms.date: 11/15/2023
10+
ms.date: 12/01/2023
1111
keywords: "VMM, Arc, Azure"
1212

1313
#Customer intent: As an IT infrastructure admin, I want to install arc agents to use Azure management services for SCVMM VMs.
@@ -51,4 +51,4 @@ An admin can install agents for multiple machines from the Azure portal if the m
5151
5252
## Next steps
5353

54-
[Recover from accidental deletion of resource bridge virtual machine](disaster-recovery.md).
54+
[Manage VM extensions to use Azure management services for your SCVMM VMs](../servers/manage-vm-extensions.md).

articles/azure-arc/system-center-virtual-machine-manager/install-arc-agents-using-script.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Install Arc agent using a script for SCVMM VMs
33
description: Learn how to enable guest management using a script for Arc enabled SCVMM VMs.
44
ms.topic: how-to
5-
ms.date: 11/29/2023
5+
ms.date: 12/01/2023
66
ms.service: azure-arc
77
author: PriskeyJeronika-MS
88
ms.author: v-gjeronika
@@ -56,4 +56,4 @@ Ensure the following before you install Arc agents using a script for SCVMM VMs:
5656
5757
## Next steps
5858
59-
[Manage VM extensions to use Azure management services](https://learn.microsoft.com/azure/azure-arc/servers/manage-vm-extensions).
59+
[Manage VM extensions to use Azure management services for your SCVMM VMs](../servers/manage-vm-extensions.md).

articles/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: jsuri
77
ms.topic: quickstart
88
ms.services: azure-arc
99
ms.subservice: azure-arc-scvmm
10-
ms.date: 11/27/2023
10+
ms.date: 12/01/2023
1111
ms.custom: references_regions
1212
---
1313

@@ -137,4 +137,5 @@ If for any reason, the appliance creation fails, you need to retry it. Run the c
137137

138138
## Next steps
139139

140-
[Create a VM](create-virtual-machine.md)
140+
- [Browse and enable SCVMM resources through Azure RBAC](enable-scvmm-inventory-resources.md).
141+
- [Create a VM using Azure Arc-enabled SCVMM](create-virtual-machine.md).

articles/azure-functions/functions-bindings-azure-sql-trigger.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -514,17 +514,16 @@ The following table explains the binding configuration properties that you set i
514514

515515
## Optional Configuration
516516

517-
In addition to the required ConnectionStringSetting [application setting](./functions-how-to-use-azure-function-app-settings.md#settings), the following optional settings can be configured for the SQL trigger:
517+
The following optional settings can be configured for the SQL trigger:
518518

519-
| App Setting | Description|
519+
[!INCLUDE [app settings to local.settings.json](../../includes/functions-host-json-section-intro.md)]
520+
521+
| Setting | Description|
520522
|---------|---------|
521523
|**Sql_Trigger_BatchSize** |The maximum number of changes processed with each iteration of the trigger loop before being sent to the triggered function. The default value is 100.|
522524
|**Sql_Trigger_PollingIntervalMs**|The delay in milliseconds between processing each batch of changes. The default value is 1000 (1 second).|
523525
|**Sql_Trigger_MaxChangesPerWorker**|The upper limit on the number of pending changes in the user table that are allowed per application-worker. If the count of changes exceeds this limit, it might result in a scale-out. The setting only applies for Azure Function Apps with [runtime driven scaling enabled](#enable-runtime-driven-scaling). The default value is 1000.|
524526

525-
526-
[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
527-
528527
## Set up change tracking (required)
529528

530529
Setting up change tracking for use with the Azure SQL trigger requires two steps. These steps can be completed from any SQL tool that supports running queries, including [Visual Studio Code](/sql/tools/visual-studio-code/mssql-extensions), [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms).

articles/azure-monitor/app/opentelemetry-add-modify.md

Lines changed: 40 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -374,8 +374,6 @@ The following table represents the currently supported custom telemetry types:
374374
> [!NOTE]
375375
> Custom Metrics are under preview in Azure Monitor Application Insights. Custom metrics without dimensions are available by default. To view and alert on dimensions, you need to [opt-in](pre-aggregated-metrics-log-metrics.md#custom-metrics-dimensions-and-pre-aggregation).
376376
377-
Consider collecting more metrics beyond what's provided by the instrumentation libraries.
378-
379377
The OpenTelemetry API offers six metric "instruments" to cover various metric scenarios and you need to pick the correct "Aggregation Type" when visualizing metrics in Metrics Explorer. This requirement is true when using the OpenTelemetry Metric API to send metrics and when using an instrumentation library.
380378

381379
The following table shows the recommended [aggregation types](../essentials/metrics-aggregation-explained.md#aggregation-types) for each of the OpenTelemetry Metric Instruments.
@@ -1380,15 +1378,51 @@ Currently unavailable.
13801378

13811379
### Send custom telemetry using the Application Insights Classic API
13821380

1383-
We recommend you use the OpenTelemetry APIs whenever possible, but there might be some scenarios when you have to use the Application Insights [Classic API](api-custom-events-metrics.md)s.
1381+
We recommend you use the OpenTelemetry APIs whenever possible, but there might be some scenarios when you have to use the Application Insights [Classic API](api-custom-events-metrics.md).
13841382

13851383
#### [ASP.NET Core](#tab/aspnetcore)
13861384

1387-
Not available in .NET.
1385+
##### Events
1386+
1387+
1. Add `Microsoft.ApplicationInsights` to your application.
1388+
1389+
2. Create a `TelemetryClient` instance.
1390+
1391+
> [!NOTE]
1392+
> It's important to only create once instance of the TelemetryClient per application.
1393+
1394+
```csharp
1395+
var telemetryConfiguration = new TelemetryConfiguration { ConnectionString = "" };
1396+
var telemetryClient = new TelemetryClient(telemetryConfiguration);
1397+
```
1398+
1399+
3. Use the client to send custom telemetry.
1400+
1401+
```csharp
1402+
telemetryClient.TrackEvent("testEvent");
1403+
```
13881404

13891405
#### [.NET](#tab/net)
13901406

1391-
Not available in .NET.
1407+
##### Events
1408+
1409+
1. Add `Microsoft.ApplicationInsights` to your application.
1410+
1411+
2. Create a `TelemetryClient` instance.
1412+
1413+
> [!NOTE]
1414+
> It's important to only create once instance of the TelemetryClient per application.
1415+
1416+
```csharp
1417+
var telemetryConfiguration = new TelemetryConfiguration { ConnectionString = "" };
1418+
var telemetryClient = new TelemetryClient(telemetryConfiguration);
1419+
```
1420+
1421+
3. Use the client to send custom telemetry.
1422+
1423+
```csharp
1424+
telemetryClient.TrackEvent("testEvent");
1425+
```
13921426

13931427
#### [Java](#tab/java)
13941428

@@ -1915,7 +1949,7 @@ Attaching custom dimensions to logs can be accomplished using a [message templat
19151949

19161950
Logback, Log4j, and java.util.logging are [autoinstrumented](#logs). Attaching custom dimensions to your logs can be accomplished in these ways:
19171951

1918-
* [Log4j 2.0 MapMessage](https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/message/MapMessage.html) (a `MapMessage` key of `"message"` is captured as the log message)
1952+
* [Log4j 2.0 MapMessage](https://logging.apache.org/log4j/2.0/javadoc/log4j-api/org/apache/logging/log4j/message/MapMessage.html) (a `MapMessage` key of `"message"` is captured as the log message)
19191953
* [Log4j 2.0 Thread Context](https://logging.apache.org/log4j/2.x/manual/thread-context.html)
19201954
* [Log4j 1.2 MDC](https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html)
19211955

0 commit comments

Comments
 (0)