Skip to content

Commit 5909aab

Browse files
authored
Merge pull request #111405 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
2 parents 57641c9 + 2a2abdb commit 5909aab

File tree

16 files changed

+77
-50
lines changed

16 files changed

+77
-50
lines changed

articles/active-directory/hybrid/how-to-connect-pta-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ If you are migrating from AD FS (or other federation technologies) to Pass-throu
116116

117117
## Can I use Pass-through Authentication in a multi-forest Active Directory environment?
118118

119-
Yes. Multi-forest environments are supported if there are forest trusts between your Active Directory forests and if name suffix routing is correctly configured.
119+
Yes. Multi-forest environments are supported if there are forest trusts (two-way) between your Active Directory forests and if name suffix routing is correctly configured.
120120

121121
## Does Pass-through Authentication provide load balancing across multiple Authentication Agents?
122122

articles/active-directory/hybrid/tshoot-connect-objectsync.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -58,11 +58,6 @@ When UserPrincipalName (UPN)/Alternate Login ID suffix is not verified with the
5858

5959
![Azure AD replaces UPN](media/tshoot-connect-objectsync/objsynch2.png)
6060

61-
### Changing UPN Suffix from one federated domain to another federated domain
62-
Azure Active Directory does not allow the synchronization of UserPrincipalName (UPN)/Alternate Login ID suffix change from one federated domain to another federated domain. This applies to domains, that are verified with the Azure AD Tenant and have the Authentication Type as Federated.
63-
64-
![No UPN synch from one federated domain to another](media/tshoot-connect-objectsync/objsynch3.png)
65-
6661
### Azure AD Tenant DirSync Feature ‘SynchronizeUpnForManagedUsers’ is disabled
6762
When the Azure AD Tenant DirSync Feature ‘SynchronizeUpnForManagedUsers’ is disabled, Azure Active Directory does not allow synchronization updates to UserPrincipalName/Alternate Login ID for licensed user accounts with managed authentication.
6863

articles/active-directory/manage-apps/application-proxy-wildcard.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ The wildcard application is represented with just one tile in the [MyApps panel]
113113

114114
### Kerberos constrained delegation
115115

116-
For applications using [kerberos constrained delegation (KCD) as the SSO method](application-proxy-configure-single-sign-on-with-kcd.md), the SPN listed for the SSO method may also need a wildcard. For example, the SPN could be: `HTTP/*.adventure-works.com`. You still need to have the individual SPNs configured on your backend servers (for example, `http://expenses.adventure-works.com and HTTP/travel.adventure-works.com`).
116+
For applications using [kerberos constrained delegation (KCD) as the SSO method](application-proxy-configure-single-sign-on-with-kcd.md), the SPN listed for the SSO method may also need a wildcard. For example, the SPN could be: `HTTP/*.adventure-works.com`. You still need to have the individual SPNs configured on your backend servers (for example, `HTTP/expenses.adventure-works.com and HTTP/travel.adventure-works.com`).
117117

118118
## Scenario 1: General wildcard application
119119

articles/azure-government/documentation-government-services-media.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,10 +44,6 @@ The "Azure Media Indexer 2 Preview" Azure Media Analytics media processor is not
4444

4545
There is no CDN integration with streaming endpoints in Azure Government DCs.
4646

47-
### Live encoding
48-
49-
Live encoding is not available in Azure Government.
50-
5147
## Next steps
5248

5349
For supplemental information and updates, subscribe to the

articles/azure-monitor/app/api-filtering-sampling.md

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -485,13 +485,41 @@ The following sample initializer sets cloud role name to every tracked telemetry
485485
```csharp
486486
public void Initialize(ITelemetry telemetry)
487487
{
488-
if(string.IsNullOrEmpty(telemetry.Context.Cloud.RoleName))
488+
if (string.IsNullOrEmpty(telemetry.Context.Cloud.RoleName))
489489
{
490490
telemetry.Context.Cloud.RoleName = "MyCloudRoleName";
491491
}
492492
}
493493
```
494494

495+
#### Add information from HttpContext
496+
497+
The following sample initializer reads data from the [`HttpContext`](https://docs.microsoft.com/aspnet/core/fundamentals/http-context?view=aspnetcore-3.1) and appends it to a `RequestTelemetry` instance. The `IHttpContextAccessor` is automatically provided through constructor dependency injection.
498+
499+
```csharp
500+
public class HttpContextRequestTelemetryInitializer : ITelemetryInitializer
501+
{
502+
private readonly IHttpContextAccessor httpContextAccessor;
503+
504+
public HttpContextRequestTelemetryInitializer(IHttpContextAccessor httpContextAccessor)
505+
{
506+
this.httpContextAccessor =
507+
httpContextAccessor ??
508+
throw new ArgumentNullException(nameof(httpContextAccessor));
509+
}
510+
511+
public void Initialize(ITelemetry telemetry)
512+
{
513+
var requestTelemetry = telemetry as RequestTelemetry;
514+
if (requestTelemetry == null) return;
515+
516+
var claims = this.httpContextAccessor.HttpContext.User.Claims;
517+
Claim oidClaim = claims.FirstOrDefault(claim => claim.Type == "oid");
518+
requestTelemetry.Properties.Add("UserOid", oidClaim?.Value);
519+
}
520+
}
521+
```
522+
495523
## ITelemetryProcessor and ITelemetryInitializer
496524

497525
What's the difference between telemetry processors and telemetry initializers?

articles/cognitive-services/QnAMaker/How-To/set-up-qnamaker-service-azure.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Endpoint keys can be managed from the [QnA Maker portal](https://qnamaker.ai).
8383
>[!NOTE]
8484
>Refresh your keys if you think they've been compromised. This may require corresponding changes to your client application or bot code.
8585
86-
### Upgrade QnA Maker SKU
86+
## Upgrade QnA Maker SKU
8787

8888
When you want to have more questions and answers in your knowledge base, beyond your current tier, upgrade your QnA Maker service pricing tier.
8989

@@ -97,7 +97,7 @@ To upgrade the QnA Maker management SKU:
9797

9898
![QnA Maker pricing](../media/qnamaker-how-to-upgrade-qnamaker/qnamaker-pricing-page.png)
9999

100-
### Upgrade App Service
100+
## Upgrade App Service
101101

102102
When your knowledge base needs to serve more requests from your client app, upgrade your App Service pricing tier.
103103

@@ -107,7 +107,7 @@ Go to the App Service resource in the Azure portal, and select the **Scale up**
107107

108108
![QnA Maker App Service scale](../media/qnamaker-how-to-upgrade-qnamaker/qnamaker-appservice-scale.png)
109109

110-
### Upgrade the Azure Cognitive Search service
110+
## Upgrade the Azure Cognitive Search service
111111

112112
If you plan to have many knowledge bases, upgrade your Azure Cognitive Search service pricing tier.
113113

@@ -213,4 +213,4 @@ If you delete any of the Azure resources used for your QnA Maker knowledge bases
213213
Learn more about the [App service](../../../app-service/index.yml) and [Search service](../../../search/index.yml).
214214

215215
> [!div class="nextstepaction"]
216-
> [Create and publish a knowledge base](../Quickstarts/create-publish-knowledge-base.md)
216+
> [Create and publish a knowledge base](../Quickstarts/create-publish-knowledge-base.md)

articles/container-registry/container-registry-helm-repos.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,18 +72,21 @@ helm create hello-world
7272
As a basic example, change directory to the `templates` folder and first delete the contents there:
7373

7474
```console
75+
cd hello-world/templates
7576
rm -rf *
7677
```
7778

7879
In the `templates` folder, create a file called `configmap.yaml` with the following contents:
7980

80-
```yml
81+
```console
82+
cat <<EOF > configmap.yaml
8183
apiVersion: v1
8284
kind: ConfigMap
8385
metadata:
8486
name: hello-world-configmap
8587
data:
8688
myvalue: "Hello World"
89+
EOF
8790
```
8891

8992
For more about creating and running this example, see [Getting Started](https://helm.sh/docs/chart_template_guide/getting_started/) in the Helm Docs.

articles/event-hubs/event-hubs-java-get-started-send.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -311,7 +311,8 @@ For different types of build environments, you can explicitly obtain the latest
311311

312312
System.out.println("End of sample");
313313
}
314-
```
314+
}
315+
```
315316
3. Create one more class called `EventProcessor`, using the following code:
316317

317318
```java

articles/event-hubs/get-started-java-send-v2.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The Java client library for Event Hubs is available in the [Maven Central Reposi
4545

4646
### Write code to send messages to the event hub
4747

48-
For the following sample, first create a new Maven project for a console/shell application in your favorite Java development environment. Add a class named `SimpleSend`, and add the following code to the class:
48+
For the following sample, first create a new Maven project for a console/shell application in your favorite Java development environment. Add a class named `Sender`, and add the following code to the class:
4949

5050
```java
5151
import com.azure.messaging.eventhubs.*;

articles/openshift/howto-using-azure-redhat-openshift.md

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,19 @@ The `az aro` extension allows you to create, access, and delete Azure Red Hat Op
6464
aro 0.3.0
6565
...
6666
```
67-
67+
68+
### Get a Red Hat pull secret (optional)
69+
70+
A Red Hat pull secret enables your cluster to access Red Hat container registries and additional content. Using a pull secret is optional but recommended.
71+
72+
To get your pull secret:
73+
74+
1. Go to https://cloud.redhat.com/openshift/install/azure/aro-provisioned.
75+
1. Log in to your Red Hat account, or create a new Red Hat account by using your business email; accept the terms and conditions.
76+
1. Select **Download pull secret**.
77+
78+
Save the *pull-secret.txt* file somewhere safe; you will use the file each time you create a cluster.
79+
6880
### Create a virtual network containing two empty subnets
6981

7082
Follow these steps to create a virtual network containing two empty subnets.
@@ -75,15 +87,7 @@ Follow these steps to create a virtual network containing two empty subnets.
7587
LOCATION=eastus #the location of your cluster
7688
RESOURCEGROUP="v4-$LOCATION" #the name of the resource group where you want to create your cluster
7789
CLUSTER=cluster #the name of your cluster
78-
PULL_SECRET="<optional-pull-secret>"
7990
```
80-
>[!NOTE]
81-
> The optional pull secret enables your cluster to access Red Hat container registries along with additional content.
82-
>
83-
> Access your pull secret by navigating to https://cloud.redhat.com/openshift/install/azure/installer-provisioned and clicking *Copy Pull Secret*.
84-
>
85-
> You will need to log in to your Red Hat account, or create a new Red Hat account with your business email and accept the terms and conditions.
86-
8791

8892
2. Create a resource group for your cluster.
8993

@@ -139,7 +143,7 @@ az aro create \
139143
--worker-subnet "$CLUSTER-worker" \
140144
--cluster-resource-group "aro-$CLUSTER" \
141145
--domain "$CLUSTER" \
142-
--pull-secret "$PULL_SECRET"
146+
--pull-secret @pull-secret.txt
143147
```
144148

145149
>[!NOTE]

0 commit comments

Comments
 (0)