Partages de fichiers cloud de classe Entreprise, simples, sécurisés et serverless
Tirez parti des partages de fichiers complètement managés dans le cloud qui sont accessibles via les protocoles SMB et NFS standard. Les partages de fichiers Azure peuvent être montés simultanément sur des déploiements cloud ou locaux de Windows, macOS et Linux. Les partages de fichiers Azure peuvent également être mis en cache sur les serveurs Windows avec Azure File Sync pour un accès rapide à proximité de l’endroit où les données sont utilisées.
Explorez les options tarifaires
Appliquez des filtres pour personnaliser les options de tarification à vos besoins.
Les prix ne sont que des estimations et ne sont pas destinés à être des devis réels. Le prix réel peut varier selon le type de contrat conclu avec Microsoft, la date d'achat et le taux de change. Les prix sont calculés en dollars américains et convertis à l'aide des taux de clôture au comptant de Londres saisis au cours des deux jours ouvrables précédant le dernier jour ouvrable de la fin du mois précédent. Si les deux jours ouvrables précédant la fin du mois tombent un jour férié sur les principaux marchés, le jour de fixation des taux est généralement le jour précédant immédiatement les deux jours ouvrables. Ce taux s'applique à toutes les transactions du mois à venir. Connectez-vous au calculateur de prix Azure pour voir les prix en fonction de votre programme/offre actuel avec Microsoft. Contactez un spécialiste des ventes Azure pour plus d'informations sur les prix ou pour demander un devis. Consultez les questions fréquemment posées sur la tarification Azure.
Les services fédéraux américains (US Government) peuvent acheter les services Azure Government auprès d’un fournisseur de solutions de licence, sans engagement financier initial, ou directement par le biais d’un abonnement en ligne avec paiement à l’utilisation.
Important : le prix en réal brésilien est donné à titre indicatif uniquement ; s’agissant d’une transaction internationale, le prix final dépend du taux de change et de la présence éventuelle de taxes. Aucun eNF ne sera émis.
Les services fédéraux américains (US Government) peuvent acheter les services Azure Government auprès d’un fournisseur de solutions de licence, sans engagement financier initial, ou directement par le biais d’un abonnement en ligne avec paiement à l’utilisation.
Important : le prix en réal brésilien est donné à titre indicatif uniquement ; s’agissant d’une transaction internationale, le prix final dépend du taux de change et de la présence éventuelle de taxes. Aucun eNF ne sera émis.
Azure Files supports two different media tiers of storage, SSD and HDD, which allow you to tailor your file shares to the performance and price requirements of your scenario:
- SSD (“premium”): File shares hosted on solid-state drives (SSDs) provide consistent high performance and low latency, within single-digit milliseconds for most IO operations.
- HDD (“standard”): File shares hosted on hard disk drives (HDDs) provide cost-effective storage for general purpose use.
Provisioned v2
In a provisioned model, the primary costs of the Azure file share are based on the amount of storage, IOPS, and throughput you provision when you create or update your file share, regardless of how much you use. With the provisioned v2 billing model, you have the ability to separately provision storage, IOPS, and throughput, although we will recommend IOPS and throughput provisioning to you based on the amount of provisioned storage you select. For more information on the provisioned v2 billing model, see understanding the provisioned v2 billing model.
| HDD (“standard”) | |
|---|---|
| Quantity | Price |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. Provisioned storage can be changed after share creation. |
$- |
|
Provisioned IOPS
The maximum IOPS, or transactions per second, of the file share. You are charged for the IOPS you’ve provisioned regardless of how many IOs you use. Provisioned IOPS can be changed after share creation. |
$- |
|
Provisioned throughput
The maximum amount of data that can be transferred per second of the file share. You are charged for the throughput you’ve provisioned regardless of what you use. Provisioned throughput can be changed after share creation. |
$- |
|
Overflow snapshot used storage
In the provisioned v2 billing model, snapshot usage that fits within the provisioned storage of the share is free. Any additional snapshot storage that doesn’t fit within the provisioned storage of the share is charged with a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. Provisioned storage can be changed after share creation. |
$- |
|
Provisioned IOPS
The maximum IOPS, or transactions per second, of the file share. You are charged for the IOPS you’ve provisioned regardless of how many IOs you use. Provisioned IOPS can be changed after share creation. |
$- |
|
Provisioned throughput
The maximum amount of data that can be transferred per second of the file share. You are charged for the throughput you’ve provisioned regardless of what you use. Provisioned throughput can be changed after share creation. |
$- |
|
Overflow snapshot used storage
In the provisioned v2 billing model, snapshot usage that fits within the provisioned storage of the share is free. Any additional snapshot storage that doesn’t fit within the provisioned storage of the share is charged with a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. Provisioned storage can be changed after share creation. |
$- |
|
Provisioned IOPS
The maximum IOPS, or transactions per second, of the file share. You are charged for the IOPS you’ve provisioned regardless of how many IOs you use. Provisioned IOPS can be changed after share creation. |
$- |
|
Provisioned throughput
The maximum amount of data that can be transferred per second of the file share. You are charged for the throughput you’ve provisioned regardless of what you use. Provisioned throughput can be changed after share creation. |
$- |
|
Overflow snapshot used storage
In the provisioned v2 billing model, snapshot usage that fits within the provisioned storage of the share is free. Any additional snapshot storage that doesn’t fit within the provisioned storage of the share is charged with a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. Provisioned storage can be changed after share creation. |
$- |
|
Provisioned IOPS
The maximum IOPS, or transactions per second, of the file share. You are charged for the IOPS you’ve provisioned regardless of how many IOs you use. Provisioned IOPS can be changed after share creation. |
$- |
|
Provisioned throughput
The maximum amount of data that can be transferred per second of the file share. You are charged for the throughput you’ve provisioned regardless of what you use. Provisioned throughput can be changed after share creation. |
$- |
|
Overflow snapshot used storage
In the provisioned v2 billing model, snapshot usage that fits within the provisioned storage of the share is free. Any additional snapshot storage that doesn’t fit within the provisioned storage of the share is charged with a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. Provisioned storage can be changed after share creation. |
$- |
|
Provisioned IOPS
The maximum IOPS, or transactions per second, of the file share. You are charged for the IOPS you’ve provisioned regardless of how many IOs you use. Provisioned IOPS can be changed after share creation. |
$- |
|
Provisioned throughput
The maximum amount of data that can be transferred per second of the file share. You are charged for the throughput you’ve provisioned regardless of what you use. Provisioned throughput can be changed after share creation. |
$- |
|
Overflow snapshot used storage
In the provisioned v2 billing model, snapshot usage that fits within the provisioned storage of the share is free. Any additional snapshot storage that doesn’t fit within the provisioned storage of the share is charged with a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
Provisioned v2 file shares are billed hourly at an hourly rate.
Monthly prices shown in the table above are based on a 730-hour month.
Provisioned v1
In a provisioned model, the primary costs of the Azure file share are based on the amount of storage, IOPS, and throughput you provision when you create or update your file share, regardless of how much you use. In the provisioned v1 billing model, there is one provisioned quantity for which you will pay for your file share: provisioned storage. When you create your file share, the provisioned IOPS and throughput available on your share are determined based on the amount of storage you provision. If you need more IOPS or throughput, you’ll need to provision additional storage. The provisioned v1 model is only available for SSD file shares. For more information on the provisioned v1 billing model, see understanding the provisioned v1 billing model.
| SSD (“premium”) | |
|---|---|
| Quantity | Price |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. The provisioned IOPS and provisioned throughput capacity of the share is dependent on the amount of storage provisioned. Provisioning can be changed after share creation. |
$- |
|
Snapshot used storage
In the provisioned v1 billing model, all snapshots are billed on a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. The provisioned IOPS and provisioned throughput capacity of the share is dependent on the amount of storage provisioned. Provisioning can be changed after share creation. |
$- |
|
Snapshot used storage
In the provisioned v1 billing model, all snapshots are billed on a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. The provisioned IOPS and provisioned throughput capacity of the share is dependent on the amount of storage provisioned. Provisioning can be changed after share creation. |
$- |
|
Snapshot used storage
In the provisioned v1 billing model, all snapshots are billed on a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. The provisioned IOPS and provisioned throughput capacity of the share is dependent on the amount of storage provisioned. Provisioning can be changed after share creation. |
$- |
|
Snapshot used storage
In the provisioned v1 billing model, all snapshots are billed on a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
|
Provisioned storage
The maximum storage size of the file share, specified in GiB. You are charged for the storage you’ve provision regardless of what you use. The provisioned IOPS and provisioned throughput capacity of the share is dependent on the amount of storage provisioned. Provisioning can be changed after share creation. |
$- |
|
Snapshot used storage
In the provisioned v1 billing model, all snapshots are billed on a usage-based charge per GiB. All snapshots are differential from the live file share and from each other. |
$- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- |
Provisioned v1 file shares are billed hourly at a monthly rate.
Hourly prices shown in the table above are based on a 730-hour month.
Reservations
The provisioned v1 billing model supports the use of reservations, which provide you with a discount on the cost of provisioned storage by committing to one year or three years of Azure Files consumption. Reservations can be purchased in increments of 10 TiB and 100 TiB for 1-year and 3-year commitment duration. All prices are per month. For more information, please see understanding reservations.
| 1-year reservation term | 3-year reservation term | |
|---|---|---|
| Reservation size | SSD (“premium”) provisioned storage | SSD (“premium”) provisioned storage |
| 10 Tio/mois | S.O. | S.O. |
| 100 Tio/mois | S.O. | S.O. |
| 10 Tio/mois | $- | $- |
| 100 Tio/mois | $- | $- |
| 10 Tio/mois | $- | $- |
| 100 Tio/mois | $- | $- |
| 10 Tio/mois | S.O. | S.O. |
| 100 Tio/mois | S.O. | S.O. |
Pay-as-you-go
In a pay-as-you-go model, the cost of the Azure file share is based on how much you use the file share, in the form of used storage, transaction, and data transfer costs. The pay-as-you-go model offers three “access tiers” on HDD (“standard”) storage which provide a way to balance the used storage versus used transaction prices:
- The transaction optimized access tier offers the lowest cost transaction pricing for transaction heavy workloads that don’t need the low latency offered by SSD file shares. The transaction optimized access tier is recommended for migrating data into file shares using the pay-as-you-go billing model.
- The hot access tier offers balanced storage and transaction pricing for workloads that have a good measure of both.
- The cool access tier offers the most cost-efficient storage pricing for storage-intensive workloads.
Pay-as-you-go is only available for HDD file shares. We recommend using the provisioned v2 billing model for new HDD file share deployments. For more information on the pay-as-you-go billing model, see understanding the pay-as-you-go billing model.
| HDD (“standard”) | |||
|---|---|---|---|
| Optimisé pour les transactions | À chaud | Sporadique | |
|
Used storage
The logical storage size of the files stored on the Azure file share. |
$- | $- | $- |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
$- | $- | $- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- | $- | $- |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Inclus | $- | $- |
|
Transactions d’écriture (Par 10 000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
$- | $- | $- |
|
Transactions de liste (Par 10 000)
Les transactions de liste sont des opérations qui énumèrent des parties du partage de fichiers, telles que les fichiers listing et les répertoires d’un partage. |
$- | $- | $- |
|
Transactions de lecture (Par 10 000)
Les transactions de lecture sont toutes les opérations qui lisent à partir du flux de données d’un fichier. |
$- | $- | $- |
|
Toutes les autres opérations (Par 10 000)
Toutes les autres opérations associées à Azure Files (partage, instantané, répertoire, etc.), à l’exception des opérations de suppression qui sont gratuites. |
$- | $- | $- |
|
Récupération de données (par Gio)
L’extraction de données donne lieu à des frais spécifiques qui s’appliquent uniquement à la l’extraction de données à partir d’un stockage sporadique. |
S.O. | S.O. | $- |
|
Used storage
The logical storage size of the files stored on the Azure file share. |
$- | $- | $- |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
$- | $- | $- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- | $- | $- |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Inclus | $- | $- |
|
Transactions d’écriture (Par 10 000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
$- | $- | $- |
|
Transactions de liste (Par 10 000)
Les transactions de liste sont des opérations qui énumèrent des parties du partage de fichiers, telles que les fichiers listing et les répertoires d’un partage. |
$- | $- | $- |
|
Transactions de lecture (Par 10 000)
Les transactions de lecture sont toutes les opérations qui lisent à partir du flux de données d’un fichier. |
$- | $- | $- |
|
Toutes les autres opérations (Par 10 000)
Toutes les autres opérations associées à Azure Files (partage, instantané, répertoire, etc.), à l’exception des opérations de suppression qui sont gratuites. |
$- | $- | $- |
|
Récupération de données (par Gio)
L’extraction de données donne lieu à des frais spécifiques qui s’appliquent uniquement à la l’extraction de données à partir d’un stockage sporadique. |
S.O. | S.O. | $- |
|
Used storage
The logical storage size of the files stored on the Azure file share. |
$- | $- | $- |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
$- | $- | $- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- | $- | $- |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Inclus | $- | $- |
|
Transactions d’écriture (Par 10 000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
$- | $- | $- |
|
Transactions de liste (Par 10 000)
Les transactions de liste sont des opérations qui énumèrent des parties du partage de fichiers, telles que les fichiers listing et les répertoires d’un partage. |
$- | $- | $- |
|
Transactions de lecture (Par 10 000)
Les transactions de lecture sont toutes les opérations qui lisent à partir du flux de données d’un fichier. |
$- | $- | $- |
|
Toutes les autres opérations (Par 10 000)
Toutes les autres opérations associées à Azure Files (partage, instantané, répertoire, etc.), à l’exception des opérations de suppression qui sont gratuites. |
$- | $- | $- |
|
Récupération de données (par Gio)
L’extraction de données donne lieu à des frais spécifiques qui s’appliquent uniquement à la l’extraction de données à partir d’un stockage sporadique. |
S.O. | S.O. | $- |
|
Used storage
The logical storage size of the files stored on the Azure file share. |
$- | $- | $- |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
$- | $- | $- |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
$- | $- | $- |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Inclus | $- | $- |
|
Transactions d’écriture (Par 10 000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
$- | $- | $- |
|
Transactions de liste (Par 10 000)
Les transactions de liste sont des opérations qui énumèrent des parties du partage de fichiers, telles que les fichiers listing et les répertoires d’un partage. |
$- | $- | $- |
|
Transactions de lecture (Par 10 000)
Les transactions de lecture sont toutes les opérations qui lisent à partir du flux de données d’un fichier. |
$- | $- | $- |
|
Toutes les autres opérations (Par 10 000)
Toutes les autres opérations associées à Azure Files (partage, instantané, répertoire, etc.), à l’exception des opérations de suppression qui sont gratuites. |
$- | $- | $- |
|
Récupération de données (par Gio)
L’extraction de données donne lieu à des frais spécifiques qui s’appliquent uniquement à la l’extraction de données à partir d’un stockage sporadique. |
S.O. | S.O. | $- |
|
Used storage
The logical storage size of the files stored on the Azure file share. |
S.O. | S.O. | S.O. |
|
Snapshot used storage
The physical storage size of the differential snapshots. |
S.O. | S.O. | S.O. |
|
Soft-deleted used storage
When a file share is soft-deleted, the used portion of the storage is charged for the indicated soft-deleted period. All other meters are not charged unless the share is restored. |
S.O. | S.O. | S.O. |
|
Metadata used storage
The file system metadata associated with files and directories such as access control lists (ACLs) or other properties. |
Inclus | S.O. | S.O. |
|
Transactions d’écriture (Par 10 000)
Write transactions are any operations which modify a file’s data stream. This category also includes file handle operations, such as opening a file handle, even if the file is being opened for read. |
S.O. | S.O. | S.O. |
|
Transactions de liste (Par 10 000)
Les transactions de liste sont des opérations qui énumèrent des parties du partage de fichiers, telles que les fichiers listing et les répertoires d’un partage. |
S.O. | S.O. | S.O. |
|
Transactions de lecture (Par 10 000)
Les transactions de lecture sont toutes les opérations qui lisent à partir du flux de données d’un fichier. |
S.O. | S.O. | S.O. |
|
Toutes les autres opérations (Par 10 000)
Toutes les autres opérations associées à Azure Files (partage, instantané, répertoire, etc.), à l’exception des opérations de suppression qui sont gratuites. |
S.O. | S.O. | S.O. |
|
Récupération de données (par Gio)
L’extraction de données donne lieu à des frais spécifiques qui s’appliquent uniquement à la l’extraction de données à partir d’un stockage sporadique. |
S.O. | S.O. | S.O. |
|
Transfert de données GRS (par Gio)
Les frais de transfert de données GRS correspondent à la bande passante utilisée pour répliquer ces données vers la région Azure secondaire. |
$- | $- | $- |
Used storage, snapshot used storage, soft-deleted used storage, and metadata used storage are billed hourly at a monthly rate. Transaction and data transfer meters are billed hourly.
Hourly prices shown in the table above are based on a 730-hour month.
Réservations
The pay-as-you-go billing model supports the use of reservations, which provide you with a discount on the cost of used storage by committing to one year or three years of Azure Files consumption. Reservations can be purchased in increments of 10 TiB and 100 TiB for 1-year and 3-year commitment duration. All prices are per month. For more information, please see understanding reservations.
| 1-year reservation term | 3-year reservation term | |||
|---|---|---|---|---|
| HDD (“standard”) used storage | ||||
| À chaud | Sporadique | À chaud | Sporadique | |
| 10 Tio/mois | $- | $- | $- | $- |
| 100 Tio/mois | $- | $- | $- | $- |
| 10 Tio/mois | $- | $- | $- | $- |
| 100 Tio/mois | $- | $- | $- | $- |
| 10 Tio/mois | $- | $- | $- | $- |
| 100 Tio/mois | $- | $- | $- | $- |
| 10 Tio/mois | $- | $- | $- | $- |
| 100 Tio/mois | $- | $- | $- | $- |
File Sync
Il s’agit des coûts de synchronisation de vos fichiers des serveurs Windows Server vers les partages Azure Files dans le cloud. En savoir plus sur Azure File Sync.
Le coût total des services Azure File Sync est déterminé par le nombre de serveurs qui se connectent aux point de terminaison cloud (Azure File Share), plus les coûts sous-jacents d’Azure Files (notamment les coûts de stockage et d’accès) et les transferts de données sortants.
Le tarif ci-dessous correspond au forfait mensuel par serveur.
| File Sync | Prix par mois |
|---|---|
| Serveur de synchronisation* | $- |
Tarification et options d’achat Azure
Connectez-vous directement avec nous
Obtenez un guide pas à pas de la tarification Azure. Comprenez la tarification de votre solution cloud, découvrez l’optimisation des coûts et demandez une offre personnalisée.
Discuter avec un spécialiste des ventesDécouvrez les modalités d'achat
Achetez des services Azure via le site web Azure, un représentant Azure ou un partenaire Azure.
Explorez vos optionsRessources supplémentaires
Fichiers Azure
En savoir plus sur les fonctionnalités et capacités Fichiers Azure.
Calculatrice de prix
Estimez vos coûts mensuels pour l’utilisation des différentes combinaisons de produits Azure.
SLA
Consultez le Contrat de niveau de service (SLA) pour Fichiers Azure.
Documentation
Consulter les didacticiels et vidéos techniques, et d’autres ressources Fichiers Azure.
Forum Aux Questions
-
Pour afficher la répartition complète des transactions SMB et FileREST, consultez À propos de la facturation Azure Files et File Sync.
Discutez avec un spécialiste des ventes pour qu’il vous explique en détail la tarification Azure. Comprendre la tarification de votre solution cloud.
Profitez de services cloud gratuits et d’un crédit de $200 pour découvrir Azure pendant 30 jours.