How to Create a Free Sandbox
Back in April, we blogged about Microsoft’s licensing changes for storage and additional instances. The changes, which are now fully in effect, included a few huge advantages to licensees – one of which we’ll be blogging about today.
Is your organization under Microsoft’s new storage model? Many of our customers are under the new model but either didn’t realize the new model included unlimited free sandbox instances or were confused about how to spin one up. Below, we walk you through the necessary steps to create a free sandbox. And by the way, if you’re not sure if your organization is running under the new storage model, just try the steps below – if you’re able to create a free sandbox, you’ll know it is!
How to Create a Free Sandbox
1. Go to your Dynamics 365 Administration center and click Try the new Admin center.
2. Click +New under Environments.
3. Name your org, select Production in the Type field, and set Create a database for this environment to Yes. Finally, click <Next>.
4. Configure your database settings as desired and add a security role (this can be done later). Click <Save>.
5. You will see your new org show up in a few minutes.
6. Once it’s ready, select it and click <Edit>.
7. Add the URL and in the Type field, select Sandbox. Click <Save>.
8. After a few minutes, you’ll see it appear in both of your admin centers, as shown below:
That’s it! And as long as you have available capacity (at least 1 GB must be free to spin up a new instance), you can do this as many times as you like.
Dynamics 365 Enterprise Edition: Licensing Changes for Storage and Additional Instances
Microsoft recently announced some pretty significant – and exciting! – licensing changes related to storage allotments and fees, as well as additional sandbox and production instances. In today’s post, we’ll walk you through these changes and how they might positively impact your organization.
Since the inception of Dynamics 365, Microsoft’s licensing model allowed for increasing storage allotments for Dynamics 365 Online in chunks – an additional 10 GB for every 20 full-access users – and charging for each additional GB of database storage needed. Additionally, they charged a fee for each additional production or non-production instance. Well, that’s all about to change…
Starting April 1st, Microsoft is evolving how they allocate, categorize, and charge for additional storage and instances in Dynamics 365 Enterprise Edition and PowerApps.
When it comes to storage for Dynamics 365, Microsoft is going to be splitting what’s currently known as “Database Storage” into three separate buckets – Database capacity, File capacity, and Log capacity – and categorizing it under the Common Data Service (CDS), which is the underlying service for Dynamics 365.
- Database capacity consists of metadata.
- File capacity refers to attachments.
- Log capacity refers to log files that are created in the system.
Currently, customers are entitled to 10 GB of storage by default and receive an additional 10 GB of storage for every 20 full-access users. Additional database storage can be purchased for $5/GB/month.
In the future, users will get 10 GB of database capacity, 20 GB of file capacity, and 2 GB of log capacity by default and receive incremental capacity for each full access user added: 250 MB of database capacity, 2 GB of file, and no additional log capacity per full access user. Additional storage can be purchased at $40/GB/month for database, $2/GB/month for file and $10/GB/month of log capacity, on an as-needed basis.
||10 GB database storage
||5 GB/20 full-access users
||250 MB/full-access user
||2 GB/full-access user
|Additional storage cost
A few things to be aware of:
- Pay close attention to the term “full user.” If your organization is Team Member license-heavy, there may be implications for your storage allotment.
- Rest assured, there is a simple method for tracking storage bucket usage. Microsoft will provide a report that shows usage, both overall and by instance. Starting April 1st, this report can be accessed through the Power Platform admin center, under the Analytics area.
The other thing that’s changing in April is how additional sandbox and production instances are handled. In the past, customers wanting additional Dynamics 365 instances had to pay per additional instance – $150/month for a sandbox instance and $500/month for a production instance. However, with this evolved model, you are now able to have as many instances as you’d like – production or sandbox – as long as you have the capacity (at least 1 GB must be free to spin up a new instance). There is no need to purchase additional instances. This is huge!
Current customers have two choices: convert to the evolved model any time after April 1st or stay on the current model until the next renewal. However, there is no model mixing – in other words, each organization as a whole must either stay on the current model or switch to the new model. Note that customers not purchasing additional storage or instances will not be affected.
There are some amazing benefits to this new model of storage and licensing:
- Customers will now have visibility (via the report in the Power Platform admin center) into precisely what is using up their data – file storage, log storage, or database storage.
- There’s no longer a need to purchase additional instances of Dynamics 365, as long as the capacity is there for an additional environment – this can save customers a lot of money!
- Additional storage is incremented by full-access user you license, not by blocks of 20 users. In the past, if you had 19 users, you still only received the 10 GB default storage. Now, your storage will be incremented for each full-access user that’s added.
As you can see, these are pretty significant changes. Changes to things like licensing, storage, and user allotments often fly under the radar, but in this case, these are exciting and potentially very impactful.
Be sure to subscribe to our blog to keep up with the latest updates.
Happy Dynamics 365’ing!
Saving Space in your Dynamics CRM Online Organization
Let's say you've received a notification that your Dynamics CRM Online has reached 80% storage usage. You could choose to purchase more storage, but you may also be wondering if there are ways to reduce storage usage. Below are a few options for saving space in Dynamics CRM.
1. Delete old audit history
If you have enabled audit history, one of the easiest ways to reduce storage usage is to delete old audit history logs. However, depending on your organizational practice and needs this isn't always possible. Generally, as a rule of thumb we recommend deleting audit history older than 6 months. Here are the steps to do it:
- Navigate to Settings >> Auditing.
- Click on Audit Log Management.
- Highlight the old audit log you wish to delete.
- Click on Delete Logs.
2. Change audit scope
You may wish to disable auditing for certain fields, entities or workflows to reduce future storage usage. If you are the org system administrator, follow these steps to disable auditing on a specific field:
- Navigate to Settings >> Customizations >> Customize the System.
- Expand Entities tab on the left-hand side of the window and then expand the specific entity where the field is located.
- Click on Fields tab, find the field for which you wish to disable auditing and double click on it.
- When the window opens click on the Disable radio button under Auditing option.
- Save then Publish.
Repeat this process for all fields you wish to disable auditing for.
To disable auditing for the entire entity, follow these steps:
- Navigate to Settings >> Customizations >> Customize the System.
- Expand Entities tab on the left-hand side of the window and click on the entity you wish to disable auditing for.
- Scroll down and uncheck the checkbox next to Auditing.
3. Delete successful workflow execution log
Another method to save storage space is to delete logs for successfully executed workflows. Note that this will not delete workflow unsuccessful execution logs in case you wish to troubleshoot the error. Depending on your organization's practices this may not be possible, but for those organizations that don't need to store these kinds of records, follow these steps to disable workflow execution logs:
- Navigate to Settings >> Processes.
- Select All Processes as the View.
- Double click on the workflow for which you wish to delete successful execution logs.
- You may have to Deactivate the Workflow before you can change settings.
- Makes sure that you check the checkbox below
This option is checked by default on background workflows and on real-time workflows this option does not exist.
4. Delete old/irrelevant data
PowerObjects does not recommend deleting data as a method of reducing storage usage. However, in specific cases deleting old or bogus data is a reasonable business decision. If you are debating whether you should delete your data or not, PowerObjects can help you determine the best decision for your business.
5. Move email attachments to SharePoint
One of the common reasons to run out of storage space are large email attachments. Did you know that with the PowerAttachment add-on you can strip email attachments, store them in SharePoint and still maintain the connection between the email message and the email attachment? This is a great solution for those organizations that are concerned about data storage cost, as storing data in SharePoint is about 10 times cheaper than storing it in Dynamics CRM! You can try PowerAttachment free for thirty days and can download it here.
6. Move photo attachments to SharePoint
Similarly, if your organization uses PowerPhoto to store multiple large images per record, you will quickly run out of space in your Dynamics CRM. Just like migrating email to SharePoint, migrating photos need not be a painful process. PowerObjects can save you money by utilizing cheaper storage location without interrupting your business processes and productivity.
Questions? Wondering what your best options are for saving space? The experts at PowerObjects are happy to help--reach out today!