Skip to content

Commit

Permalink
Merge pull request #3831 from debghs/t
Browse files Browse the repository at this point in the history
fix: typo
  • Loading branch information
NikCharlebois authored Oct 25, 2023
2 parents a58b818 + f0a9625 commit d0efc22
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/docs/home/what-is-M365DSC.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Microsoft365DSC is the very first PowerShell project that natively supports Reve

Upon providing credentials with correct permissions, the tool will begin the extraction of the configuration. Once it completes the extraction, it will prompt you to specify a destination directory to store the extracted artifacts.

The tool will extract several artifacts, including all SharePoint Add-ins and Frameworks packages, the configuration itself, and a metadata file that contains all variables that are specific to your environment. That metadata file (.psd1) abstracts components of you configuration, such as the tenant name, in order to make it as easy as possible for you to replicate those configurations across tenants. As an example, you can extract the configuration from any given tenant using the ReverseDSC functionality, open the extracted .psd1 metadata file, change the tenant's name to a new destination, and apply that new configuration. This allows organizations to keep the configuration of multiple tenants in synchronization with one another.
The tool will extract several artifacts, including all SharePoint Add-ins and Frameworks packages, the configuration itself, and a metadata file that contains all variables that are specific to your environment. That metadata file (.psd1) abstracts components of your configuration, such as the tenant name, in order to make it as easy as possible for you to replicate those configurations across tenants. As an example, you can extract the configuration from any given tenant using the ReverseDSC functionality, open the extracted .psd1 metadata file, change the tenant's name to a new destination, and apply that new configuration. This allows organizations to keep the configuration of multiple tenants in synchronization with one another.

See the [Exporting](../../user-guide/get-started/snapshot-of-existing-tenant/) page for more information about possible options.

Expand Down

0 comments on commit d0efc22

Please sign in to comment.