Skip to content

Commit ef9a544

Browse files
authored
Merge pull request #73779 from MicrosoftDocs/release-stack-migration
Stack Migration - PR MicrosoftDocs#1
2 parents 893a632 + 442b6b4 commit ef9a544

13 files changed

+1469
-9
lines changed

.openpublishing.redirection.json

Lines changed: 1460 additions & 0 deletions
Large diffs are not rendered by default.

articles/active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ After you associate a subscription to a different directory, there might be addi
7272

7373
1. If you have any key vaults, you must change the key vault tenant ID. For more information, see [Change a key vault tenant ID after a subscription move](../../key-vault/key-vault-subscription-move-fix.md).
7474

75-
2. If you have registered an Azure Stack using this subscription, you must re-register. For more information, see [Register Azure Stack with Azure](../../azure-stack/azure-stack-registration.md).
75+
2. If you have registered an Azure Stack using this subscription, you must re-register. For more information, see [Register Azure Stack with Azure](/azure-stack/operator/azure-stack-registration).
7676

7777

7878

articles/azure-resource-manager/templates-cloud-consistency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -669,5 +669,5 @@ Consider the following tips for testing and automation:
669669

670670
## Next steps
671671

672-
* [Azure Resource Manager template considerations](../azure-stack/user/azure-stack-develop-templates.md)
672+
* [Azure Resource Manager template considerations](/azure-stack/user/azure-stack-develop-templates)
673673
* [Best practices for Azure Resource Manager templates](resource-group-authoring-templates.md)

articles/backup/backup-mabs-install-azure-stack.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ If shared with other virtual machines, the storage account size and IOPS limits
5757
Each Azure Stack virtual machine comes with temporary disk storage, which is available to the user as volume `D:\`. The local staging area needed by Azure Backup can be configured to reside in `D:\`, and the cache location can be placed on `C:\`. In this way, no storage needs to be carved away from the data disks attached to the Azure Backup Server virtual machine.
5858

5959
### Storing backup data on local disk and in Azure
60-
Azure Backup Server stores backup data on Azure disks attached to the virtual machine, for operational recovery. Once the disks and storage space are attached to the virtual machine, Azure Backup Server manages storage for you. The amount of backup data storage depends on the number and size of disks attached to each [Azure Stack virtual machine](../azure-stack/user/azure-stack-storage-overview.md). Each size of Azure Stack VM has a maximum number of disks that can be attached to the virtual machine. For example, A2 is four disks. A3 is eight disks. A4 is 16 disks. Again, the size and number of disks determines the total backup storage pool.
60+
Azure Backup Server stores backup data on Azure disks attached to the virtual machine, for operational recovery. Once the disks and storage space are attached to the virtual machine, Azure Backup Server manages storage for you. The amount of backup data storage depends on the number and size of disks attached to each [Azure Stack virtual machine](/azure-stack/user/azure-stack-storage-overview). Each size of Azure Stack VM has a maximum number of disks that can be attached to the virtual machine. For example, A2 is four disks. A3 is eight disks. A4 is 16 disks. Again, the size and number of disks determines the total backup storage pool.
6161

6262
> [!IMPORTANT]
6363
> You should **not** retain operational recovery (backup) data on Azure Backup Server-attached disks for more than five days.
@@ -69,7 +69,7 @@ To store backup data in Azure, create or use a Recovery Services vault. When pre
6969

7070
### Scaling deployment
7171
If you want to scale your deployment, you have the following options:
72-
- Scale up - Increase the size of the Azure Backup Server virtual machine from A series to D series, and increase the local storage [per the Azure Stack virtual machine instructions](../azure-stack/user/azure-stack-manage-vm-disks.md).
72+
- Scale up - Increase the size of the Azure Backup Server virtual machine from A series to D series, and increase the local storage [per the Azure Stack virtual machine instructions](/azure-stack/user/azure-stack-manage-vm-disks).
7373
- Offload data - send older data to Azure and retain only the newest data on the storage attached to the Azure Backup Server.
7474
- Scale out - Add more Azure Backup Servers to protect the workloads.
7575

articles/cognitive-services/cognitive-services-container-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The [Computer Vision](Computer-vision/Home.md), [Face](Face/Overview.md), [Text
2929

3030
- **Control over data**: Allow customers to choose where these Cognitive Services process their data. This is essential for customers that cannot send data to the cloud but need access to Cognitive Services technology. Support consistency in hybrid environments – across data, management, identity, and security.
3131
- **Control over model updates**: Provide customers flexibility in versioning and updating of models deployed in their solutions.
32-
- **Portable architecture**: Enable the creation of a portable application architecture that can be deployed on Azure, on-premises and the edge. Containers can be deployed directly to [Azure Kubernetes Service](../aks/index.yml), [Azure Container Instances](../container-instances/index.yml), or to a [Kubernetes](https://kubernetes.io/) cluster deployed to [Azure Stack](../azure-stack/index.yml). For more information, see [Deploy Kubernetes to Azure Stack](../azure-stack/user/azure-stack-solution-template-kubernetes-deploy.md).
32+
- **Portable architecture**: Enable the creation of a portable application architecture that can be deployed on Azure, on-premises and the edge. Containers can be deployed directly to [Azure Kubernetes Service](../aks/index.yml), [Azure Container Instances](../container-instances/index.yml), or to a [Kubernetes](https://kubernetes.io/) cluster deployed to [Azure Stack](/azure/azure-stack). For more information, see [Deploy Kubernetes to Azure Stack](/azure-stack/user/azure-stack-solution-template-kubernetes-deploy).
3333
- **High throughput / low latency**: Provide customers the ability to scale for high throughput and low latency requirements by enabling Cognitive Services to run physically close to their application logic and data. Containers do not cap transactions per second (TPS) and can be made to scale both up and out to handle demand if you provide the necessary hardware resources.
3434

3535

articles/guides/operations/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121
- name: Azure Stack
2222
items:
2323
- name: Azure Stack deployment overview
24-
href: ../../azure-stack/azure-stack-deploy-overview.md
24+
href: /azure-stack/operator/azure-stack-deploy-overview
2525
- name: Azure Backup
2626
items:
2727
- name: Backup a VM in Azure Portal

articles/storage/blobs/data-lake-storage-explorer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Select **Add an Azure Account** and click **Sign in..**. Follow the on-screen pr
3535

3636
![Microsoft Azure Storage Explorer - Connect window](media/storage-quickstart-blobs-storage-explorer/connect.png)
3737

38-
When it completes connecting, Azure Storage Explorer loads with the **Explorer** tab shown. This view gives you insight to all of your Azure storage accounts as well as local storage configured through the [Azure Storage Emulator](../common/storage-use-emulator.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json), [Cosmos DB](../../cosmos-db/storage-explorer.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) accounts, or [Azure Stack](../../azure-stack/user/azure-stack-storage-connect-se.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) environments.
38+
When it completes connecting, Azure Storage Explorer loads with the **Explorer** tab shown. This view gives you insight to all of your Azure storage accounts as well as local storage configured through the [Azure Storage Emulator](../common/storage-use-emulator.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json), [Cosmos DB](../../cosmos-db/storage-explorer.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) accounts, or [Azure Stack](/azure-stack/user/azure-stack-storage-connect-se?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) environments.
3939

4040
![Microsoft Azure Storage Explorer - Connect window](media/storage-quickstart-blobs-storage-explorer/mainpage.png)
4141

articles/storage/blobs/storage-quickstart-blobs-storage-explorer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Select **Add an Azure Account** and click **Sign in..**. Follow the on-screen pr
3535

3636
![Microsoft Azure Storage Explorer - Connect window](media/storage-quickstart-blobs-storage-explorer/connect.png)
3737

38-
When it completes connecting, Azure Storage Explorer loads with the **Explorer** tab shown. This view gives you insight to all of your Azure storage accounts as well as local storage configured through the [Azure Storage Emulator](../common/storage-use-emulator.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json), [Cosmos DB](../../cosmos-db/storage-explorer.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) accounts, or [Azure Stack](../../azure-stack/user/azure-stack-storage-connect-se.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) environments.
38+
When it completes connecting, Azure Storage Explorer loads with the **Explorer** tab shown. This view gives you insight to all of your Azure storage accounts as well as local storage configured through the [Azure Storage Emulator](../common/storage-use-emulator.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json), [Cosmos DB](../../cosmos-db/storage-explorer.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) accounts, or [Azure Stack](/azure-stack/user/azure-stack-storage-connect-se?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) environments.
3939

4040
![Microsoft Azure Storage Explorer - Connect window](media/storage-quickstart-blobs-storage-explorer/mainpage.png)
4141

includes/cognitive-services-containers-host-computer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,4 @@ The **host** is a x64-based computer that runs the docker container. It can be a
1010

1111
* [Azure Kubernetes Service](../articles/aks/index.yml)
1212
* [Azure Container Instances](../articles/container-instances/index.yml)
13-
* [Kubernetes](https://kubernetes.io/) cluster deployed to [Azure Stack](../articles/azure-stack/index.yml). For more information, see [Deploy Kubernetes to Azure Stack](../articles/azure-stack/user/azure-stack-solution-template-kubernetes-deploy.md).
13+
* [Kubernetes](https://kubernetes.io/) cluster deployed to [Azure Stack](/azure/azure-stack). For more information, see [Deploy Kubernetes to Azure Stack](../articles/azure-stack/user/azure-stack-solution-template-kubernetes-deploy.md).

0 commit comments

Comments
 (0)