Skip to content

Commit 0eed601

Browse files
Merge pull request #312040 from v-thepet/links2-19
BULK - Broken link fixes
2 parents fafb06d + adea5c9 commit 0eed601

8 files changed

Lines changed: 20 additions & 20 deletions

File tree

articles/azure-vmware/ecosystem-back-up-vms.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Back up network traffic between Azure VMware Solution VMs and the backup reposit
2626

2727
You can find more information on these backup solutions here:
2828
- [Cohesity](https://www.cohesity.com/blogs/expanding-cohesitys-support-for-microsofts-ecosystem-azure-stack-and-azure-vmware-solution/)
29-
- [Commvault](https://documentation.commvault.com/v11/software/azure_vmware_solution.html)
29+
- [Commvault](https://documentation.commvault.com/11.40/software/azure_vmware_solution.html)
3030
- [Dell PPDM](https://www.dell.com/support/manuals/en-us/enterprise-copy-data-management/pp-dm_19.19_virtual_machines_ug/azure-vmware-solution-avs-on-microsoft-azure?guid=guid-600e65ba-95f3-4d7c-b8bb-4950abf2f9ad&lang=en-us)
3131
- [Rubrik](https://www.rubrik.com/en/products/cloud-data-management)
3232
- [Veeam](https://www.veeam.com/kb4012)

articles/batch/batch-task-output-file-conventions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ For other scenarios, you might want to consider a different approach. For more i
3131

3232
## What is the Batch File Conventions standard?
3333

34-
The [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files) provides a naming scheme for the destination containers and blob paths to which your output files are written. Files persisted to Azure storage that follow the standard are [automatically viewable in the Azure portal](#view-output-files-in-the-azure-portal).
34+
The [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files) provides a naming scheme for the destination containers and blob paths to which your output files are written. Files persisted to Azure storage that follow the standard are [automatically viewable in the Azure portal](#view-output-files-in-the-azure-portal).
3535

3636
The File Conventions library for .NET automatically names your storage containers and task output files according to the standard. The library also provides methods to query output files in Azure Storage. You can query by job ID, task ID, or purpose.
3737

@@ -176,7 +176,7 @@ foreach (CloudTask task in myJob.ListTasks())
176176

177177
## View output files in the Azure portal
178178

179-
If your task output files use the [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files), you can view the files in the Azure portal.
179+
If your task output files use the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files), you can view the files in the Azure portal.
180180

181181
To enable the display of your output files in the portal, you must satisfy the following requirements:
182182

@@ -210,7 +210,7 @@ The [PersistOutputs](https://github.com/Azure/azure-batch-samples/tree/master/CS
210210

211211
The Batch File Conventions library for .NET is available on [NuGet](https://www.nuget.org/packages/Microsoft.Azure.Batch.Conventions.Files). The library extends the [CloudJob](/dotnet/api/microsoft.azure.batch.cloudjob) and [CloudTask](/dotnet/api/microsoft.azure.batch.cloudtask) classes with new methods. For more information, see the [File Conventions library reference documentation](/dotnet/api/microsoft.azure.batch.conventions.files).
212212

213-
The [File Conventions library source code](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files) is available on GitHub.
213+
The [File Conventions library source code](/dotnet/api/microsoft.azure.batch.conventions.files) is available on GitHub.
214214

215215
### Next steps
216216

articles/batch/batch-task-output-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Azure Batch provides more than one way to persist task output. Using the Batch s
2626
- You want to write code to persist task output from within your client application, without modifying the application that your task is running.
2727
- You want to persist output from Batch tasks and job manager tasks in pools created with the virtual machine configuration.
2828
- You want to persist output to an Azure Storage container with an arbitrary name.
29-
- You want to persist output to an Azure Storage container named according to the [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files).
29+
- You want to persist output to an Azure Storage container named according to the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files).
3030

3131
If your scenario differs from those listed above, you may need to consider a different approach. For example, the Batch service API does not currently support streaming output to Azure Storage while the task is running. To stream output, consider using the Batch File Conventions library, available for .NET. For other languages, you'll need to implement your own solution. For more information about other options, see [Persist job and task output to Azure Storage](batch-task-output.md).
3232

@@ -190,7 +190,7 @@ there are many contributing factors to upload performance, including the size of
190190

191191
## Use the Batch service API with the Batch File Conventions standard
192192

193-
When you persist task output with the Batch service API, you can name your destination container and blobs however you like. You can also choose to name them according to the [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files). The File Conventions standard determines the names of the destination container and blob in Azure Storage for a given output file based on the names of the job and task. If you do use the File Conventions standard for naming output files, then your output files are available for viewing in the [Azure portal](https://portal.azure.com).
193+
When you persist task output with the Batch service API, you can name your destination container and blobs however you like. You can also choose to name them according to the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files). The File Conventions standard determines the names of the destination container and blob in Azure Storage for a given output file based on the names of the job and task. If you do use the File Conventions standard for naming output files, then your output files are available for viewing in the [Azure portal](https://portal.azure.com).
194194
195195
If you are developing in C#, you can use the methods built into the [Batch File Conventions library for .NET](https://www.nuget.org/packages/Microsoft.Azure.Batch.Conventions.Files). This library creates the properly named containers and blob paths for you. For example, you can call the API to get the correct name for the container, based on the job name:
196196

articles/batch/batch-task-output.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ For more information, see [Persist task data to Azure Storage with the Batch ser
3636

3737
### Batch File Conventions library
3838

39-
The [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files#conventions) is an optional set of conventions for naming task output files in Azure Storage. The standard provides naming conventions for a file's destination container and blob path, based on the names of the job and task.
39+
The [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files) is an optional set of conventions for naming task output files in Azure Storage. The standard provides naming conventions for a file's destination container and blob path, based on the names of the job and task.
4040

4141
It's optional to use the File Conventions standard for naming your output data files. You can choose to name the destination container and blob path instead. If you do use the File Conventions standard, then you can view your output files in the [Azure portal](https://portal.azure.com).
4242

@@ -46,7 +46,7 @@ For more information, see [Persist job and task data to Azure Storage with the B
4646

4747
### Batch File Conventions standard
4848

49-
If you're using a language other than .NET, you can implement the [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files#conventions) in your own application. Use this approach when:
49+
If you're using a language other than .NET, you can implement the [Batch File Conventions standard](/dotnet/api/microsoft.azure.batch.conventions.files) in your own application. Use this approach when:
5050

5151
- You want to use a common naming scheme.
5252
- You want to view task output in the [Azure portal](https://portal.azure.com).

articles/expressroute/expressroute-locations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -375,7 +375,7 @@ If you're remote and don't have fiber connectivity, or you want to explore other
375375
| **[QSC AG](https://www2.qbeyond.de/en/)** |Interxion | Frankfurt |
376376
| **[RETN](https://retn.net/products/cloud-connect)** | Equinix | Amsterdam |
377377
| **Rogers** | Cologix<br/>Equinix | Montreal<br/>Toronto |
378-
| **[Spectrum Enterprise](https://enterprise.spectrum.com/services/networking/cloud-connectivity)** | Equinix | Chicago<br/>Dallas<br/>Los Angeles<br/>New York<br/>Silicon Valley |
378+
| **[Spectrum Enterprise](https://enterprise.spectrum.com/products/networking/connectivity/cloud-connect.html)** | Equinix | Chicago<br/>Dallas<br/>Los Angeles<br/>New York<br/>Silicon Valley |
379379
| **[Tamares Telecom](https://www.exelera.net/)** | Equinix | London |
380380
| **[Tata Teleservices](https://www.tatatelebusiness.com/data-services/ez-cloud-connect/)** | Tata Communications | Chennai<br/>Mumbai |
381381
| **[TDC Erhverv](https://tdc.dk/)** | Equinix | Amsterdam |

articles/nat-gateway/monitor-nat-gateway.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ This table describes how you can collect data to monitor your service, and what
2020

2121
|Data to collect|Description|How to collect and route the data|Where to view the data|Supported data|
2222
|---------|---------|---------|---------|---------|
23-
|Metric data|Metrics are numerical values that describe an aspect of a system at a particular point in time. Metrics can be aggregated using algorithms, compared to other metrics, and analyzed for trends over time.| You can export metric data using the [Azure Monitor REST API](/azure/azure-monitor/essentials/rest-api-walkthrough). Metrics can be obtained by [data collection rules](/azure/azure-monitor/data-collection/data-collection-metrics?tabs=log-analytics-workspaces). This feature is currently in preview.|[Metrics explorer](/azure/azure-monitor/essentials/metrics-getting-started)| [Azure NAT Gateway metrics supported by Azure Monitor](/azure/nat-gateway/monitor-nat-gateway-reference#metrics)|
24-
|Activity log data|The Azure Monitor activity log provides insight into subscription-level events. The activity log includes information like when a resource is modified or a virtual machine is started.| You can export activity log data using the [Azure Monitor REST API](/azure/azure-monitor/essentials/rest-api-walkthrough). Activity logs can be obtained by [data collection rules](/azure/azure-monitor/data-collection/data-collection-metrics?tabs=log-analytics-workspaces). This feature is currently in preview.|[Activity log](/azure/azure-monitor/essentials/activity-log)| |
23+
|Metric data|Metrics are numerical values that describe an aspect of a system at a particular point in time. Metrics can be aggregated using algorithms, compared to other metrics, and analyzed for trends over time.| You can export metric data using the [Azure Monitor REST API](/azure/azure-monitor/essentials/rest-api-walkthrough). Metrics can be obtained by [data collection rules](/azure/azure-monitor/data-collection/data-collection-rule-overview). This feature is currently in preview.|[Metrics explorer](/azure/azure-monitor/essentials/metrics-getting-started)| [Azure NAT Gateway metrics supported by Azure Monitor](/azure/nat-gateway/monitor-nat-gateway-reference#metrics)|
24+
|Activity log data|The Azure Monitor activity log provides insight into subscription-level events. The activity log includes information like when a resource is modified or a virtual machine is started.| You can export activity log data using the [Azure Monitor REST API](/azure/azure-monitor/essentials/rest-api-walkthrough). Activity logs can be obtained by [data collection rules](/azure/azure-monitor/data-collection/data-collection-rule-overview). This feature is currently in preview.|[Activity log](/azure/azure-monitor/essentials/activity-log)| |
2525

2626
[!INCLUDE [azmon-horz-supported-data](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/azmon-horz-supported-data.md)]
2727

articles/networking/networking-partners-msp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Use the links in this section for more information about managed cloud networkin
3636
|[Deutsche Telekom](https://cloud.telekom.de/de/infrastruktur/microsoft-azure/azure-networking)|[Network connectivity to Azure: 2-Hr assessment](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/telekomdeutschlandgmbh1617272539503.azure_netzwerkoptimierung_2_stunden?search=telekom&page=1); [Cloud Transformation with Azure: 1-Day Workshop](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/telekomdeutschlandgmbh1617272539503.azure_cloudtransformation_1_tag?search=telekom&page=1)|[Managed ExpressRoute](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/telekomdeutschlandgmbh1617272539503.azure_intraselect_cloud_connect_implementation?search=telekom&page=1)|||[Azure Networking and Security: 1-Day Workshop](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/telekomdeutschlandgmbh1617272539503.azure_netzwerke_und_sicherheit_1_tag?search=telekom&page=1); [Intraselect SecureConnect: 1-Week Implementation](https://appsource.microsoft.com/de-de/marketplace/consulting-services/telekomdeutschlandgmbh1617272539503.azure_intraselect_secure_connect_implementation?tab=Overview)|
3737
|[Equinix](https://www.equinix.com/)|Cloud Optimized WAN Workshop|[ExpressRoute Connectivity Strategy Workshop](https://www.equinix.se/resources/data-sheets/expressroute-strategy-workshop); [Equinix Cloud Exchange Fabric](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/equinix.equinix_ecx_fabric?tab=Overview)||||
3838
|[Federated Wireless](https://www.federatedwireless.com/)||||[Federated Wireless Connectivity-as-a-Service](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/federatedwireless1580839623708.fw_caas?tab=Overview)|
39-
|[HCL](https://www.hcltech.com/)|HCL Cloud Network Transformation- One Day Assessment|[1-Hour Briefing of HCL Azure ExpressRoute Service](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/hcl-technologies.hclmanagedazureexpressroute?tab=Overview)|[HCL Azure Virtual WAN Services - One Day Assessment](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/hcl-technologies.hclmanagedazurevitualwan?search=vWAN&page=1)|[HCL Azure Private LTE offering - One Day Assessment](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/hcl-technologies.hclazureprivatelteoffering)|
39+
|[HCL](https://www.hcltech.com/)|HCL Cloud Network Transformation- One Day Assessment|1-Hour Briefing of HCL Azure ExpressRoute Service|HCL Azure Virtual WAN Services - One Day Assessment|[HCL Azure Private LTE offering - One Day Assessment](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/hcl-technologies.hclazureprivatelteoffering)|
4040
|[IIJ](https://www.iij.ad.jp/biz/cloudex/)|[ExpressRoute implementation: 1-Hour Briefing](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/internet_initiative_japan_inc.iij_cxm_consulting)|[ExpressRoute: 2-Week Implementation](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/internet_initiative_japan_inc.iij_cxmer_consulting)||||
4141
|[Infosys](https://www.infosys.com/services/microsoft-cloud-business/pages/index.aspx)|[Infosys Integrate+ for Azure](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/infosysltd.infosys-integrate-for-azure?tab=Overview)|||||
4242
|[Digital Realty (formerly Interxion)](https://www.digitalrealty.com/partners/microsoft-azure)|[Azure Networking Assessment - Five Days](https://azuremarketplace.microsoft.com/en-us/marketplace/consulting-services/interxionhq.inxn_azure_networking_assessment)|||||

0 commit comments

Comments
 (0)