[stg] ../fileservices/ > /rest/api/storageservices/fileservices/

articles/storage/storage-import-export-creating-an-export-job.md

@@ -55,7 +55,7 @@ Creating an export job for the Microsoft Azure Import/Export service using the R
 
  Follow the steps below to obtain the shipping location:  
 
--   Identify the name of the location of your storage account. This value can be found under the **Location** field on the storage account’s **Dashboard** in the classic portal or queried for by using the service management API operation [Get Storage Account Properties](../fileservices/Get%20Storage%20Account%20Properties1.md).  
+-   Identify the name of the location of your storage account. This value can be found under the **Location** field on the storage account’s **Dashboard** in the classic portal or queried for by using the service management API operation [Get Storage Account Properties](/rest/api/storagerp/storageaccounts#StorageAccounts_GetProperties).  
 
 -   Retrieve a list of locations that are available to process this storage account by calling the `List Locations` operation with the query parameter `originlocation=<location-name>`. The list returned will contain one or more locations to which you can ship your drives.  
 

articles/storage/storage-import-export-creating-an-import-job.md

@@ -60,7 +60,7 @@ Creating an import job for the Microsoft Azure Import/Export service using the R
 
  Follow the steps below to obtain the shipping location:  
 
--   Identify the name of the location of your storage account. This value can be found under the **Location** field on the storage account’s **Dashboard** in the classic portal or queried for by using the service management API operation [Get Storage Account Properties](../fileservices/Get%20Storage%20Account%20Properties1.md).  
+-   Identify the name of the location of your storage account. This value can be found under the **Location** field on the storage account’s **Dashboard** in the classic portal or queried for by using the service management API operation [Get Storage Account Properties](/rest/api/storagerp/storageaccounts#StorageAccounts_GetProperties).  
 
 -   Retrieve a list of locations that are available to process this storage account by calling the `List Locations` operation with the query parameter `originlocation=<location-name>`. The list returned will contain one or more locations to which you can ship your drives.  
 

articles/storage/storage-import-export-file-format-manifest.md

@@ -116,7 +116,7 @@ block-list ::=
 |`PageRange/@Offset`|Attribute, Integer|Specifies the offset in the transfer file and the blob where the specified page range begins. This value must be a multiple of 512.|  
 |`PageRange/@Length`|Attribute, Integer|Specifies the length of the page range. This value must be a multiple of 512 and no more than 4 MB.|  
 |`PageRange/@Hash`|Attribute, String|Specifies the Base16-encoded MD5 hash value for the page range.|  
-|`BlockList`|Nested XML element|Required for a block blob with named blocks.<br /><br /> For an import operation, the block list specifies a set of blocks that will be imported into Azure Storage. For an export operation, the block list specifies where each block has been stored in the file on the export disk. Each block is described by an offset in the file and a block length; each block is furthermore named by a block ID attribute, and contains an MD5 hash for the block. Up to 50,000 blocks may be used to describe a blob.  All blocks must be ordered by offset, and together should cover the complete range of the file, *i.e.*, there must be no gap between blocks. If the blob is no more than 64 MB, the block IDs for each block must be either all absent or all present. Block IDs are required to be Base64-encoded strings. See [Put Block](../fileservices/Put%20Block.md) for further requirements for block IDs.|  
+|`BlockList`|Nested XML element|Required for a block blob with named blocks.<br /><br /> For an import operation, the block list specifies a set of blocks that will be imported into Azure Storage. For an export operation, the block list specifies where each block has been stored in the file on the export disk. Each block is described by an offset in the file and a block length; each block is furthermore named by a block ID attribute, and contains an MD5 hash for the block. Up to 50,000 blocks may be used to describe a blob.  All blocks must be ordered by offset, and together should cover the complete range of the file, *i.e.*, there must be no gap between blocks. If the blob is no more than 64 MB, the block IDs for each block must be either all absent or all present. Block IDs are required to be Base64-encoded strings. See [Put Block](/rest/api/storageservices/fileservices/put-block) for further requirements for block IDs.|  
 |`Block`|XML element|Represents a block.|  
 |`Block/@Offset`|Attribute, Integer|Specifies the offset where the specified block begins.|  
 |`Block/@Length`|Attribute, Integer|Specifies the number of bytes in the block; this value must be no more than 4MB.|  

articles/storage/storage-import-export-file-format-metadata-and-properties.md

@@ -66,4 +66,4 @@ You can specify metadata and properties for one or more blobs as part of an impo
 |`Content-Language`|String|Optional. The blob's content language.|  
 |`Cache-Control`|String|Optional. The cache control string for the blob.|  
 
- See [Set Blob Properties](../fileservices/Set%20Blob%20Properties.md), [Set Blob Metadata](../fileservices/Set%20Blob%20Metadata.md), and [Setting and Retrieving Properties and Metadata for Blob Resources](../fileservices/Setting%20and%20Retrieving%20Properties%20and%20Metadata%20for%20Blob%20Resources.md) for detailed rules about setting blob metadata and properties.
+ See [Set Blob Properties](/rest/api/storageservices/fileservices/set-blob-properties), [Set Blob Metadata](/rest/api/storageservices/fileservices/set-blob-metadata), and [Setting and Retrieving Properties and Metadata for Blob Resources](/rest/api/storageservices/fileservices/setting-and-retrieving-properties-and-metadata-for-blob-resources) for detailed rules about setting blob metadata and properties.

articles/storage/storage-import-export-tool-preparing-hard-drives-import-v1.md

@@ -132,7 +132,7 @@ To prepare one or more hard drives for an import job, follow these steps:
 |Command line parameter|Description|  
 |----------------------------|-----------------|  
 |**/srcdir:**<SourceDirectory\>|`Required.` The source directory that contains files to be copied to the target drive. The directory path must be an absolute path (not a relative path).|  
-|**/dstdir:**<DestinationBlobVirtualDirectory\>|`Required.` The path to the destination virtual directory in your Windows Azure storage account. The virtual directory may or may not already exist.<br /><br /> You can specify a container, or a blob prefix like `music/70s/`. The destination directory must begin with the container name, followed by a forward slash "/", and optionally may include a virtual blob directory that ends with "/".<br /><br /> When the destination container is the root container, you must explicitly specify the root container, including the forward slash, as `$root/`. Since blobs under the root container cannot include "/" in their names, any subdirectories in the source directory will not be copied when the destination directory is the root container.<br /><br /> Be sure to use valid container names when specifying destination virtual directories or blobs. Keep in mind that container names must be lowercase. For container naming rules, see [Naming and Referencing Containers, Blobs, and Metadata](../fileservices/Naming%20and%20Referencing%20Containers,%20Blobs,%20and%20Metadata.md).|  
+|**/dstdir:**<DestinationBlobVirtualDirectory\>|`Required.` The path to the destination virtual directory in your Windows Azure storage account. The virtual directory may or may not already exist.<br /><br /> You can specify a container, or a blob prefix like `music/70s/`. The destination directory must begin with the container name, followed by a forward slash "/", and optionally may include a virtual blob directory that ends with "/".<br /><br /> When the destination container is the root container, you must explicitly specify the root container, including the forward slash, as `$root/`. Since blobs under the root container cannot include "/" in their names, any subdirectories in the source directory will not be copied when the destination directory is the root container.<br /><br /> Be sure to use valid container names when specifying destination virtual directories or blobs. Keep in mind that container names must be lowercase. For container naming rules, see [Naming and Referencing Containers, Blobs, and Metadata](/rest/api/storageservices/fileservices/naming-and-referencing-containers--blobs--and-metadata).|  
 |**/Disposition:**<rename&#124;no-overwrite&#124;overwrite>|`Optional.` Specifies the behavior when a blob with the specified address already exists. Valid values for this parameter are: `rename`, `no-overwrite` and `overwrite`. Note that these values are case-sensitive. If no value is specified, the default is `rename`.<br /><br /> The value specified for this parameter affects all the files in the directory specified by the `/srcdir` parameter.|  
 |**/BlobType:**<BlockBlob&#124;PageBlob>|`Optional.` Specifies the blob type for the destination blobs. Valid values are: `BlockBlob` and `PageBlob`. Note that these values are case-sensitive. If no value is specified, the default is `BlockBlob`.<br /><br /> In most cases, `BlockBlob` is recommended. If you specify `PageBlob`, the length of each file in the directory must be a multiple of 512, the size of a page for page blobs.|  
 |**/PropertyFile:**<PropertyFile\>|`Optional.` Path to the property file for the destination blobs. See [Import-Export Service Metadata and Properties File Format](storage-import-export-file-format-metadata-and-properties.md) for more information.|  
@@ -144,7 +144,7 @@ To prepare one or more hard drives for an import job, follow these steps:
 |Command line parameter|Description|  
 |----------------------------|-----------------|  
 |**/srcfile:**<SourceFile\>|`Required.` The full path to the file to be copied. The directory path must be an absolute path (not a relative path).|  
-|**/dstblob:**<DestinationBlobPath\>|`Required.` The path to the destination blob in your Windows Azure storage account. The blob may or may not already exist.<br /><br /> Specify the blob name beginning with the container name. The blob name cannot start with "/" or the storage account name. For blob naming rules, see [Naming and Referencing Containers, Blobs, and Metadata](../fileservices/Naming%20and%20Referencing%20Containers,%20Blobs,%20and%20Metadata.md).<br /><br /> When the destination container is the root container, you must explicitly specify `$root` as the container, such as `$root/sample.txt`. Note that blobs under the root container cannot include "/" in their names.|  
+|**/dstblob:**<DestinationBlobPath\>|`Required.` The path to the destination blob in your Windows Azure storage account. The blob may or may not already exist.<br /><br /> Specify the blob name beginning with the container name. The blob name cannot start with "/" or the storage account name. For blob naming rules, see [Naming and Referencing Containers, Blobs, and Metadata](/rest/api/storageservices/fileservices/naming-and-referencing-containers--blobs--and-metadata).<br /><br /> When the destination container is the root container, you must explicitly specify `$root` as the container, such as `$root/sample.txt`. Note that blobs under the root container cannot include "/" in their names.|  
 |**/Disposition:**<rename&#124;no-overwrite&#124;overwrite>|`Optional.` Specifies the behavior when a blob with the specified address already exists. Valid values for this parameter are: `rename`, `no-overwrite` and `overwrite`. Note that these values are case-sensitive. If no value is specified, the default is `rename`.|  
 |**/BlobType:**<BlockBlob&#124;PageBlob>|`Optional.` Specifies the blob type for the destination blobs. Valid values are: `BlockBlob` and `PageBlob`. Note that these values are case-sensitive. If no value is specified, the default is `BlockBlob`.<br /><br /> In most cases, `BlockBlob` is recommended. If you specify `PageBlob`, the length of each file in the directory must be a multiple of 512, the size of a page for page blobs.|  
 |**/PropertyFile:**<PropertyFile\>|`Optional.` Path to the property file for the destination blobs. See [Import-Export Service Metadata and Properties File Format](storage-import-export-file-format-metadata-and-properties.md) for more information.|  

articles/storage/storage-import-export-tool-reviewing-job-status-v1.md

@@ -19,7 +19,7 @@ ms.author: renash
 ---
 
 # Reviewing Job Status with Copy Log Files
-When the Microsoft Azure Import/Export service processes drives associated with an import or export job, it writes copy log files to the storage account to or from which you are importing or exporting blobs. The log file contains detailed status about each file that was imported or exported. The URL to each copy log file is returned when you query the status of a completed job; see [Get Job](/rest/api/storageservices/importexport/Get-Job3) for more information.  
+When the Microsoft Azure Import/Export service processes drives associated with an import or export job, it writes copy log files to the storage account to or from which you are importing or exporting blobs. The log file contains detailed status about each file that was imported or exported. The URL to each copy log file is returned when you query the status of a completed job; see [Get Job](/rest/api/storageservices`Get-Job3) for more information.  
 
  The following are example URLs for copy log files for an import job with two drives: