Skip to content

Commit ff402cd

Browse files
committed
1644082, fixed Broken external links.
1 parent e7085b1 commit ff402cd

31 files changed

+42
-42
lines changed

docs/boards/work-items/guidance/cmmi/guidance-manage-issues-cmmi.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ You can use the issue work item to help you track problems with the project plan
5555
If the issue has not been successfully resolved, rework the corrective action tasks, and assign them to suitable personnel for resolution. Reconsider the priority of the issue, and consider raising it to expedite resolution and to avoid additional delay.
5656

5757
## Additional resources
58-
For more information about SCAMPI appraisals, see the following Web page: [Software Engineering Institute](https://go.microsoft.com/fwlink/?LinkId=179026).
58+
For more information about SCAMPI appraisals, see the following Web page: [Software Engineering Institute](https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9247).
5959

6060
## Related articles
6161
[Fields that track bugs, issues, and risks (CMMI)](guidance-bugs-issues-risks-field-reference-cmmi.md)

docs/extend/develop/add-dashboard-widget.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -640,7 +640,7 @@ If you have already published the extension before this point, you can repackage
640640

641641
### Step 7: Add Widget From the Catalog
642642

643-
Now, go to your team dashboard at `https://dev.azure.com/{yourOrganization}/{yourProject}`. If this page is already open, then refresh it.
643+
Now, go to your team dashboard at `https:\//dev.azure.com/{yourOrganization}/{yourProject}`. If this page is already open, then refresh it.
644644
Hover on the Edit button in the bottom right, and select the Add button. This should open the widget catalog where you find the widget you installed.
645645
Choose your widget and select the 'Add' button to add it to your dashboard.
646646

docs/extend/reference/client/api/TFS/Core/Contracts/WebApiConnectedService.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,5 +32,5 @@ Extends: [WebApiConnectedServiceRef](../../../tfs/distributedtask/contracts/weba
3232

3333
* `project`: [TeamProjectReference](../../../TFS/DistributedTask/Contracts/TeamProjectReference.md). The project associated with this service
3434

35-
* `serviceUri`: string. Optional uri to connect directly to the service such as https://windows.azure.com
35+
* `serviceUri`: string. Optional uri to connect directly to the service such as https:\//windows.azure.com
3636

docs/extend/reference/client/api/TFS/Core/Contracts/WebApiConnectedServiceDetails.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,5 +24,5 @@ Extends: [WebApiConnectedServiceRef](../../../tfs/distributedtask/contracts/weba
2424

2525
* `credentialsXml`: string. Credential info
2626

27-
* `endPoint`: string. Optional uri to connect directly to the service such as https://windows.azure.com
27+
* `endPoint`: string. Optional uri to connect directly to the service such as https:\//windows.azure.com
2828

docs/extend/reference/client/api/TFS/DistributedTask/Contracts/WebApiConnectedService.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,5 +32,5 @@ Extends: [WebApiConnectedServiceRef](../../../TFS/DistributedTask/Contracts/WebA
3232

3333
* `project`: [TeamProjectReference](../../../TFS/DistributedTask/Contracts/TeamProjectReference.md). The project associated with this service
3434

35-
* `serviceUri`: string. Optional uri to connect directly to the service such as https://windows.azure.com
35+
* `serviceUri`: string. Optional uri to connect directly to the service such as https:\//windows.azure.com
3636

docs/extend/reference/client/api/TFS/DistributedTask/Contracts/WebApiConnectedServiceDetails.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,5 +24,5 @@ Extends: [WebApiConnectedServiceRef](../../../TFS/DistributedTask/Contracts/WebA
2424

2525
* `credentialsXml`: string. Credential info
2626

27-
* `endPoint`: string. Optional uri to connect directly to the service such as https://windows.azure.com
27+
* `endPoint`: string. Optional uri to connect directly to the service such as https:\//windows.azure.com
2828

docs/integrate/how-to/call-rest-api.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -147,11 +147,11 @@ You should get a response like this.
147147
The response is [JSON](https://json.org/).
148148
That's generally what you'll get back from the REST APIs,
149149
although there are a few exceptions,
150-
like [Git blobs](https://visualstudio.microsoft.com/docs/integrate/api/repos/git/blobs).
150+
like [Git blobs](/rest/api/azure/devops/git/blobs).
151151

152152
Now you should be able to look around the specific
153153
[API areas](/rest/api/azure/devops/git/) like [work item tracking](/rest/api/azure/devops/wit/)
154-
or [Git](https://visualstudio.microsoft.com/docs/integrate/api/repos/git/overview) and get to the resources that you need.
154+
or [Git](/rest/api/azure/devops/git/) and get to the resources that you need.
155155
Keep reading to learn more about the general patterns that are used in these APIs.
156156

157157
## HTTP verbs

docs/integrate/previous-apis/git/overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -133,5 +133,5 @@ In case you're looking for something not found in the **Common tasks** section a
133133
* [Trees](./trees.md)
134134

135135
>[!NOTE]
136-
>For more information on Git, see [Use Git with Visual Studio and Team Foundation Server](https://visualstudio.microsoft.com/docs/repos/git/overview).
136+
>For more information on Git, see [Use Git with Visual Studio and Team Foundation Server](../../repos/git/overview-2013).
137137

docs/integrate/previous-apis/overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ There are many ways to authenticate your application or service with Team Servic
6060
|---------------------|-------------|---------|-------------------------|--------|
6161
| Interactive client-side | GUI based client side application | Windows app enumerating bugs for a user | [Active Directory authentication library (ADAL)](https://docs.microsoft.com/azure/active-directory/develop/active-directory-authentication-libraries) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/ManagedClientConsoleAppSample) |
6262
| Interactive Javascript | GUI based Javascript application | AngularJS single page app displaying work items for a user | [ADAL](https://docs.microsoft.com/azure/active-directory/develop/active-directory-authentication-libraries) | sample (coming soon) |
63-
| Non-interactive client-side | Headless text only client side application | Console app displaying all bugs assigned to a user | [Device Profile](https://azure.microsoft.com/resources/samples/active-directory-dotnet-deviceprofile/?v=17.23h) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/DeviceProfileSample) |
63+
| Non-interactive client-side | Headless text only client side application | Console app displaying all bugs assigned to a user | [Device Profile](/samples/azure-samples/active-directory-dotnetcore-devicecodeflow-v2/invoke-protected-api-text/) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/DeviceProfileSample) |
6464
| Interactive web | GUI based web application | Custom Web dashboard displaying build summaries |[OAuth](https://docs.microsoft.com/azure/devops/integrate/get-started/authentication/oauth) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/OAuthWebSample) |
6565
| TFS application | TFS app using the Client OM library | TFS extension displaying team bug dashboards | [Client Libraries](https://docs.microsoft.com/azure/devops/integrate/concepts/dotnet-client-libraries) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/ClientLibraryConsoleAppSample) |
6666
| [TFS Extension](https://www.visualstudio.com/docs/integrate/extensions/get-started/node#files) | TFS extension | [Agile Cards](https://marketplace.visualstudio.com/items?itemName=spartez.agile-cards) | [VSS Web Extension SDK](https://github.com/Microsoft/vss-web-extension-sdk) | [sample walkthrough](https://www.visualstudio.com/docs/integrate/extensions/develop/add-dashboard-widget) |

docs/integrate/rest-api-overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ There are many ways to authenticate your application or service with Azure DevOp
6666
|---------------------|-------------|---------|-------------------------|--------|
6767
| Interactive client-side | GUI based client side application | Windows app enumerating bugs for a user | [Active Directory authentication library (ADAL)](/azure/active-directory/develop/active-directory-authentication-libraries) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/ManagedClientConsoleAppSample) |
6868
| Interactive Javascript | GUI based Javascript application | AngularJS single page app displaying work items for a user | [ADAL](/azure/active-directory/develop/active-directory-authentication-libraries) | sample (coming soon) |
69-
| Non-interactive client-side | Headless text only client side application | Console app displaying all bugs assigned to a user | [Device Profile](https://azure.microsoft.com/resources/samples/active-directory-dotnet-deviceprofile/?v=17.23h) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/DeviceProfileSample) |
69+
| Non-interactive client-side | Headless text only client side application | Console app displaying all bugs assigned to a user | [Device Profile](/samples/azure-samples/active-directory-dotnetcore-devicecodeflow-v2/invoke-protected-api-text/) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/DeviceProfileSample) |
7070
| Interactive web | GUI based web application | Custom Web dashboard displaying build summaries |[OAuth](./get-started/authentication/oauth.md) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/OAuthWebSample) |
7171
| TFS application | TFS app using the Client OM library | TFS extension displaying team bug dashboards | [Client Libraries](./get-started/client-libraries/dotnet.md) | [sample](https://github.com/Microsoft/vsts-auth-samples/tree/master/ClientLibraryConsoleAppSample) |
7272
| [Azure DevOps Services Extension](../extend/get-started/node.md) | Azure DevOps Services extension | [Agile Cards](https://marketplace.visualstudio.com/items?itemName=spartez.agile-cards) | [VSS Web Extension SDK](https://github.com/Microsoft/vss-web-extension-sdk) | [sample walkthrough](../extend/develop/add-dashboard-widget.md) |

docs/organizations/accounts/use-personal-access-tokens-to-authenticate.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ For non-Microsoft tools that integrate into Azure DevOps but don't support Micro
3838

3939
### Q: What is my Azure DevOps Services URL?
4040

41-
A: https://dev.azure.com/{yourorganization}
41+
A: https:\//dev.azure.com/{yourorganization}
4242

4343
### Q: Can I regenerate a PAT?
4444

docs/organizations/settings/azure-devops-auditing.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -138,9 +138,9 @@ When you're filtering through audit events, it’s best to leverage the “area
138138
### Areas
139139

140140
> [!Note]
141-
> While aduiting is in a public preview, we're working hard to get more areas audited. New auditing events are being added monthly.
141+
> While auditing is in a public preview, we're working hard to get more areas audited. New auditing events are being added monthly.
142142
>
143-
> If you can't find the auditing event you're looking for in the below table, be sure to check the REST API as well https://auditservice.dev.azure.com/{YOUR_ORGANIZATION}/_apis/audit/actions. Just replace {YOUR_ORGANIZATION} with the name of your organization. The API will show a list of all audit events your organization could emit.
143+
> If you can't find the auditing event you're looking for in the below table, be sure to check the REST API as well https:\//auditservice.dev.azure.com/{YOUR_ORGANIZATION}/_apis/audit/actions. Just replace {YOUR_ORGANIZATION} with the name of your organization. The API will show a list of all audit events your organization could emit.
144144
145145
|Area |Description |
146146
|----------------|------------|

docs/pipelines/archive/release/previous-version/manage-your-release.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ that contain these servers.
114114
With Visual Studio 2015, you can use
115115
[Windows PowerShell](https://msdn.microsoft.com/library/dd835506%28v=vs.85%29.aspx),
116116
Windows PowerShell Desired State Configuration
117-
([DSC](https://technet.microsoft.com/library/dn249912.aspx)),
117+
([DSC](/powershell/scripting/dsc/configurations/configurations)),
118118
or [Chef](https://www.getchef.com/) to deploy to a server without a deployment agent.
119119
If you already deploy using any of these tools,
120120
you can use the same scripts with Release Management. Or, you can use deployment agents

docs/pipelines/archive/release/previous-version/release-without-agents.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ monikerRange: '>= tfs-2013'
2020
If you want to use
2121
[Windows PowerShell](https://msdn.microsoft.com/library/dd835506%28v=vs.85%29.aspx),
2222
Windows PowerShell Desired State Configuration
23-
([DSC](https://technet.microsoft.com/library/dn249912.aspx)),
23+
([DSC](/powershell/scripting/dsc/configurations/configurations)),
2424
or [Chef](https://www.getchef.com/) to deploy your app,
2525
follow these steps. If you are using deployment agents,
2626
go **[here](release-with-agents.md)**

docs/pipelines/tasks/deploy/chef.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Use this task in a build or release pipeline to deploy to Chef environments by e
3232
<table><thead><tr><th>Argument</th><th>Description</th></tr></thead>
3333
<tr><td>Chef Connection</td><td>(Required) Name of the Chef subscription</td></tr>
3434
<tr><td>Environment</td><td>(Required) Name of the Chef Environment to be used for Deployment. The attributes of that environment will be edited.</td></tr>
35-
<tr><td>Environment Attributes</td><td>(Required) Specify the value of the leaf node attribute(s) to be updated. Example. { &quot;default_attributes.connectionString&quot; : &quot;$(connectionString)&quot;, &quot;override_attributes.buildLocation&quot; : &quot;<a href="https://sample.blob.core.windows.net/build" data-raw-source="https://sample.blob.core.windows.net/build">https://sample.blob.core.windows.net/build</a>&quot; }. Task fails if the leaf node does not exist.</td></tr>
35+
<tr><td>Environment Attributes</td><td>(Required) Specify the value of the leaf node attribute(s) to be updated. Example. { &quot;default_attributes.connectionString&quot; : &quot;$(connectionString)&quot;, &quot;override_attributes.buildLocation&quot; : &quot;https:\//sample.blob.core.windows.net/build&quot; }. Task fails if the leaf node does not exist.</td></tr>
3636
<tr><td>Wait Time</td><td>(Required) The amount of time (in minutes) to wait for this task to complete. Default value: 30 minutes</td></tr>
3737

3838

docs/pipelines/tasks/test/xamarin-test-cloud.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -42,15 +42,15 @@ None
4242
| -------- | ----------- |
4343
| **App File** | - If you want to test a single app, choose **...** and select the .apk file.<br />- If you want to test multiple apps, specify a match pattern filter. You can use a single-folder wildcard (`*`) and recursive wildcards (`**`). For example, `**/*.apk` searches for all .apk files in all subdirectories. |
4444
| **dSYM File** | To make crash logs easier to read, upload a .dSYM file that is associated with your app. Specify a path relative to the .ipa file. You can use a match pattern filter. For example: `*.dSYM`<br />**Note:** This argument applies only to iOS apps. |
45-
| **Team API Key** | Your Xamarin Test Cloud Team API key. To get it, go to your [Xamarin Test Cloud account](https://testcloud.xamarin.com/account), and then to **Teams & Apps**.<br />**Important:** Use a [secret variable](../../build/variables.md) to avoid exposing this value. |
46-
| **User Email** | Email address of your [Xamarin Test Cloud account](https://testcloud.xamarin.com/account). |
47-
| **Devices** | The devices string generated by Xamarin Test Cloud. To get this string:<br />- Go to your [Xamarin Test Cloud account](https://testcloud.xamarin.com/account).<br />- Choose **New Test Run**.<br />- Step through the wizard.<br />- When you reach the final page, copy the ID that follows the **--devices** option. |
45+
| **Team API Key** | Your Xamarin Test Cloud Team API key. To get it, go to your [Xamarin Test Cloud account](https://testcloud.xamarin.com/), and then to **Teams & Apps**.<br />**Important:** Use a [secret variable](../../build/variables.md) to avoid exposing this value. |
46+
| **User Email** | Email address of your [Xamarin Test Cloud account](https://testcloud.xamarin.com/). |
47+
| **Devices** | The devices string generated by Xamarin Test Cloud. To get this string:<br />- Go to your [Xamarin Test Cloud account](https://testcloud.xamarin.com/).<br />- Choose **New Test Run**.<br />- Step through the wizard.<br />- When you reach the final page, copy the ID that follows the **--devices** option. |
4848
| **Series** | Series name for the test run. For example, `master`, `production`, or `beta`. See [Xamarin: Creating A Test Run for a Team](https://developer.xamarin.com/guides/testcloud/organizations-and-teams/creating-a-test-run/). |
4949
| **Test Assembly Directory** | Relative path to the folder that contains the test assemblies. For example: `SolutionName/TestsProjectName/bin/Release`. |
5050
| **Advanced - Parallelization** | Select None, By test fixture, or By test method. |
5151
| **Advanced - System Language** | Select your language. If it isn't displayed, select Other and then enter its locale below. For example: `en_AU`. |
5252
| **Advanced - test-cloud.exe Location** | Location of test-cloud.exe. In most cases leave this set to the default value. |
53-
| **Advanced - Optional Arguments** | (Optional) Arguments passed to test-cloud.exe. See [Submitting UITests at the Command Line](https://developer.xamarin.com/guides/testcloud/uitest/working-with/submitting-tests-at-command-line/). |
53+
| **Advanced - Optional Arguments** | (Optional) Arguments passed to test-cloud.exe. See [Submitting UITests at the Command Line](/xamarin/tools/ci/teamcity#submitting-xamarinuitests-to-test-cloud). |
5454
| **Advanced - Publish results to VSO/TFS** | Select if you want to pass the **--nunit-xml** option to test-cloud.exe so that results from the NUnit xml file are be published to TFS or Azure Pipelines. |
5555
| **Control options** | See [Control options](../../process/tasks.md#controloptions) |
5656

docs/reference/customize-wit-form.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ See the following topics to make the indicated customizations:
8888
witadmin exportwitd /collection:CollectionURL /p:ProjectName /n:TypeName /f:"DirectoryPath/FileName.xml"
8989
```
9090
91-
An example of a <em>CollectionURL</em> for an organization is https://dev.azure.com/*OrganizationName*.
91+
An example of a <em>CollectionURL</em> for an organization is https:\//dev.azure.com/*OrganizationName*.
9292
9393
3. Edit the file. For details, see [WebLayout XML elements](xml/weblayout-xml-elements.md).
9494

docs/reference/tfs-ps-sync/administrate-integration-tfs-project-server.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.date: 01/12/2017
2020
As an administrator for the integration of Visual Studio Team Foundation Server (TFS) and Microsoft Project Server, you must configure the integration of the two server products. When you configure this integration, you define what components participate in data synchronization and what data flows from projects to enterprise project plans. The initial configuration requires that you install software, grant permissions, register instances of Project Web Access or Project Web App (PWA), and map Project Server components to Team Foundation components. You might also need to customize the types of work items and how fields are mapped to participate in data synchronization. After you configure the integration, you might need to monitor and troubleshoot it.
2121

2222
> [!NOTE]
23-
> You can download a virtual machine that demonstrates how you can integrate TFS and Project Server 2010 so that teams can share data between the two server products. This virtual machine includes enterprise project plans in Project Server that are mapped to projects in Team Foundation Server, along with sample data to highlight key integration scenarios. The walkthrough documents illustrate four scenarios that simulate the interactions between the project manager, who is working in Project Server, and members of the software development team, who are working in TFS. For more information, see the following page on the Microsoft website: [TFS 2010 and Microsoft Project Server 2010 Integration Hyper-V Virtual Machine](https://go.microsoft.com/fwlink/?LinkID=196413).
23+
> You can download a virtual machine that demonstrates how you can integrate TFS and Project Server 2010 so that teams can share data between the two server products. This virtual machine includes enterprise project plans in Project Server that are mapped to projects in Team Foundation Server, along with sample data to highlight key integration scenarios. The walkthrough documents illustrate four scenarios that simulate the interactions between the project manager, who is working in Project Server, and members of the software development team, who are working in TFS. For more information, see the following page on the Microsoft website: [TFS 2010 and Microsoft Project Server 2010 Integration Hyper-V Virtual Machine](https://www.microsoft.com/download/details.aspx?id=22267).
2424
2525
## <a name="Setup"></a> Setup and configuration
2626

0 commit comments

Comments
 (0)