Skip to content

Commit b15e8f8

Browse files
authored
Merge branch 'main' into alexbuckgit/docutune-autopr-docs-link-absolute-20220914-221837-7570068
2 parents defc2ee + e53e209 commit b15e8f8

30 files changed

+71
-51
lines changed

articles/azure-government/compliance/azure-services-in-fedramp-auditscope.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -291,9 +291,7 @@ This article provides a detailed list of Azure, Dynamics 365, Microsoft 365, and
291291
| [Azure Information Protection](/azure/information-protection/) ****** | ✅ | ✅ | ✅ | ✅ | ✅ |
292292
| [Azure Kubernetes Service (AKS)](../../aks/index.yml) | ✅ | ✅ | ✅ | ✅ | ✅ |
293293
| [Azure Maps](../../azure-maps/index.yml) | ✅ | ✅ | ✅ | ✅ | |
294-
| [Azure Monitor](../../azure-monitor/index.yml) | ✅ | ✅ | ✅ | ✅ | ✅ |
295-
| Azure Monitor [Application Insights](../../azure-monitor/app/app-insights-overview.md) | | | | | ✅ |
296-
| Azure Monitor [Log Analytics](../../azure-monitor/logs/data-platform-logs.md) | ✅ | ✅ | ✅ | ✅ | ✅ |
294+
| [Azure Monitor](../../azure-monitor/index.yml) (incl. [Application Insights](../../azure-monitor/app/app-insights-overview.md), [Log Analytics](../../azure-monitor/logs/data-platform-logs.md)) | ✅ | ✅ | ✅ | ✅ | ✅ |
297295
| [Azure NetApp Files](../../azure-netapp-files/index.yml) | ✅ | ✅ | ✅ | ✅ | |
298296
| [Azure Policy](../../governance/policy/index.yml) | ✅ | ✅ | ✅ | ✅ | ✅ |
299297
| [Azure Policy's guest configuration](../../governance/machine-configuration/overview.md) | ✅ | ✅ | ✅ | ✅ | |

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

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -479,6 +479,21 @@ public void Initialize(ITelemetry telemetry)
479479
}
480480
}
481481
```
482+
483+
#### Control the client IP address used for gelocation mappings
484+
485+
The following sample initializer sets the client IP which will be used for geolocation mapping, instead of the client socket IP address, during telemetry ingestion.
486+
487+
```csharp
488+
public void Initialize(ITelemetry telemetry)
489+
{
490+
var request = telemetry as RequestTelemetry;
491+
if (request == null) return true;
492+
request.Context.Location.Ip = "{client ip address}"; // Could utilize System.Web.HttpContext.Current.Request.UserHostAddress;
493+
return true;
494+
}
495+
```
496+
482497
## ITelemetryProcessor and ITelemetryInitializer
483498

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

articles/azure-monitor/vm/vminsights-dependency-agent-maintenance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,4 +123,4 @@ Since the Dependency agent works at the kernel level, support is also dependent
123123
124124
## Next steps
125125
126-
If you want to stop monitoring your VMs for a while or remove VM insights entirely, see [Disable monitoring of your VMs in VM insights](../vm/vminsights-optout.md).
126+
If you want to stop monitoring your VMs for a while or remove VM insights entirely, see [Disable monitoring of your VMs in VM insights](../vm/vminsights-optout.md).

articles/azure-vmware/azure-vmware-solution-platform-updates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -169,4 +169,4 @@ For more information on this vCenter version, see [VMware vCenter Server 6.7 Upd
169169
>This is non-disruptive and should not impact Azure VMware Services or workloads. During maintenance, various VMware alerts, such as _Lost network connectivity on DVPorts_ and _Lost uplink redundancy on DVPorts_, appear in vCenter Server and clear automatically as the maintenance progresses.
170170
171171
## Post update
172-
Once complete, newer versions of VMware components appear. If you notice any issues or have any questions, contact our support team by opening a support ticket.
172+
Once complete, newer versions of VMware components appear. If you notice any issues or have any questions, contact our support team by opening a support ticket.

articles/cognitive-services/autoscale.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Autoscale feature is available for the following services:
6767

6868
* [Computer Vision](computer-vision/index.yml)
6969
* [Language](language-service/overview.md) (only available for sentiment analysis, key phrase extraction, named entity recognition, and text analytics for health)
70-
* [Form Recognizer](/azure/applied-ai-services/form-recognizer/overview?tabs=v3-0)
70+
* [Form Recognizer](../applied-ai-services/form-recognizer/overview.md?tabs=v3-0)
7171

7272
### Can I test this feature using a free subscription?
7373

articles/communication-services/tutorials/file-sharing-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Note that the tutorial above assumes that your Azure blob storage container allo
6464

6565
For downloading the files you upload to Azure blob storage, you can use shared access signatures (SAS). A shared access signature (SAS) provides secure delegated access to resources in your storage account. With a SAS, you have granular control over how a client can access your data.
6666

67-
The downloadable [GitHub sample](https://github.com/Azure-Samples/communication-services-javascript-quickstarts/tree/main/ui-library-filesharing-chat-composite) showcases the use of SAS for creating SAS URLs to Azure Storage contents. Additionally, you can [read more about SAS](/azure/storage/common/storage-sas-overview).
67+
The downloadable [GitHub sample](https://github.com/Azure-Samples/communication-services-javascript-quickstarts/tree/main/ui-library-filesharing-chat-composite) showcases the use of SAS for creating SAS URLs to Azure Storage contents. Additionally, you can [read more about SAS](../../storage/common/storage-sas-overview.md).
6868

6969
UI Library requires a React environment to be setup. Next we will do that. If you already have a React App, you can skip this section.
7070

@@ -340,4 +340,4 @@ You may also want to:
340340
- [Add chat to your app](../quickstarts/chat/get-started.md)
341341
- [Creating user access tokens](../quickstarts/access-tokens.md)
342342
- [Learn about client and server architecture](../concepts/client-and-server-architecture.md)
343-
- [Learn about authentication](../concepts/authentication.md)
343+
- [Learn about authentication](../concepts/authentication.md)

articles/event-grid/availability-zones-disaster-recovery.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,8 @@ Event Grid also provides [diagnostic logs schemas](diagnostic-logs.md) and [metr
6363

6464
## More information
6565

66-
You may find more information availability zone resiliency and disaster recovery in Azure Event Grid in our [FAQ](/azure/event-grid/event-grid-faq).
66+
You may find more information availability zone resiliency and disaster recovery in Azure Event Grid in our [FAQ](./event-grid-faq.yml).
6767

6868
## Next steps
6969

70-
- If you want to implement your own disaster recovery plan for Azure Event Grid topics and domains, see [Build your own disaster recovery for custom topics in Event Grid](custom-disaster-recovery.md).
70+
- If you want to implement your own disaster recovery plan for Azure Event Grid topics and domains, see [Build your own disaster recovery for custom topics in Event Grid](custom-disaster-recovery.md).

articles/event-grid/configure-custom-topic.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ You can use similar steps to enable an identity for an event grid domain.
7070
1. On the left menu, select **Configuration** under **Settings**.
7171
1. 2. For **Data residency**, select whether you don't want any data to be replicated to another region (**Regional**) or you want the metadata to be replicated to a predefined secondary region (**Cross-Geo**).
7272

73-
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](/azure/event-grid/event-grid-faq).
73+
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
7474

7575
If you select the **Regional** option, you may define your own disaster recovery plan. For more information, see [Build your own disaster recovery plan for Azure Event Grid topics and domains](custom-disaster-recovery.md).
7676

@@ -91,4 +91,4 @@ See the following samples to learn about publishing events to and consuming even
9191
- [Azure Event Grid samples for Java](/samples/azure/azure-sdk-for-java/eventgrid-samples/)
9292
- [Azure Event Grid samples for Python](/samples/azure/azure-sdk-for-python/eventgrid-samples/)
9393
- [Azure Event Grid samples for JavaScript](/samples/azure/azure-sdk-for-js/eventgrid-javascript/)
94-
- [Azure Event Grid samples for TypeScript](/samples/azure/azure-sdk-for-js/eventgrid-typescript/)
94+
- [Azure Event Grid samples for TypeScript](/samples/azure/azure-sdk-for-js/eventgrid-typescript/)

articles/event-grid/create-custom-topic.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.custom: mode-ui
1010
This article shows how to create a custom topic or a domain in Azure Event Grid.
1111

1212
## Prerequisites
13-
If you new to Azure Event Grid, read through [Event Grid overview](overview.md) before starting this tutorial.
13+
If you're new to Azure Event Grid, read through [Event Grid overview](overview.md) before starting this tutorial.
1414

1515
[!INCLUDE [event-grid-register-provider-portal.md](../../includes/event-grid-register-provider-portal.md)]
1616

@@ -72,7 +72,7 @@ On the **Security** page of the **Create Topic** or **Create Event Grid Domain*
7272

7373
:::image type="content" source="./media/create-custom-topic/data-residency.png" alt-text="Screenshot showing the Data residency section of the Advanced page in the Create Topic wizard.":::
7474

75-
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](/azure/event-grid/event-grid-faq).
75+
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
7676

7777
If you select the **Regional** option, you may define your own disaster recovery plan. For more information, see [Build your own disaster recovery plan for Azure Event Grid topics and domains](custom-disaster-recovery.md).
7878
3. Select **Next: Tags** to move to the **Tags** page.

articles/frontdoor/best-practices.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This article summarizes best practices for using Azure Front Door.
2020

2121
### Avoid combining Traffic Manager and Front Door
2222

23-
For most solutions, you should use *either* Front Door *or* [Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview).
23+
For most solutions, you should use *either* Front Door *or* [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md).
2424

2525
Traffic Manager is a DNS-based load balancer. It sends traffic directly to your origin's endpoints. In contrast, Front Door terminates connections at points of presence (PoPs) near to the client and establishes separate long-lived connections to the origins. The products work differently and are intended for different use cases.
2626

@@ -62,7 +62,7 @@ For more information, see [Select the certificate for Azure Front Door to deploy
6262

6363
### Use the same domain name on Front Door and your origin
6464

65-
Front Door can rewrite the `Host` header of incoming requests. This feature can be helpful when you manage a set of customer-facing custom domain names that route to a single origin. The feature can also help when you want to avoid configuring custom domain names in Front Door and at your origin. However, when you rewrite the `Host` header, request cookies and URL redirections might break. In particular, when you use platforms like Azure App Service, features like [session affinity](/azure/app-service/configure-common#configure-general-settings) and [authentication and authorization](/azure/app-service/overview-authentication-authorization) might not work correctly.
65+
Front Door can rewrite the `Host` header of incoming requests. This feature can be helpful when you manage a set of customer-facing custom domain names that route to a single origin. The feature can also help when you want to avoid configuring custom domain names in Front Door and at your origin. However, when you rewrite the `Host` header, request cookies and URL redirections might break. In particular, when you use platforms like Azure App Service, features like [session affinity](../app-service/configure-common.md#configure-general-settings) and [authentication and authorization](../app-service/overview-authentication-authorization.md) might not work correctly.
6666

6767
Before you rewrite the `Host` header of your requests, carefully consider whether your application is going to work correctly.
6868

@@ -104,4 +104,4 @@ For more information, see [Supported HTTP methods for health probes](health-prob
104104

105105
## Next steps
106106

107-
Learn how to [create an Front Door profile](create-front-door-portal.md).
107+
Learn how to [create an Front Door profile](create-front-door-portal.md).

0 commit comments

Comments
 (0)