Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Storage space requirement for "store exact copies of email on timeline" in CI-J?

(3) ShareShare
ReportReport
Posted on by 128
How much storage space is occupied by the feature "store exact copies of email on timeline" in CI-J?
 
This feature is not very well documented. Does anyone know if there is any intelligence in how this is stored/compressed? Or is it as bad as multiplying number of emails with average size? For instance half a million emails a months with average storage need growing by 50GB per month? Or even worse, also including images to make an exact copy and making the storage requirement even larger?
  • Verified answer
    Daivat Vartak (v-9davar) Profile Picture
    6,642 Super User 2025 Season 1 on at
    Storage space requirement for "store exact copies of email on timeline" in CI-J?
    Hello CU03091316-0,
     

    You've raised a very important question about the storage implications of the "store exact copies of email on timeline" feature in Customer Insights - Journeys (CI-J). Unfortunately, you're right – the documentation on this feature is sparse, and the potential for significant storage consumption is a real concern.

    Understanding the Storage Implications:

    • Exact Copies:

      • The feature aims to store exact copies, meaning it likely captures the full email content, including HTML, text, attachments, and embedded images.
      • This is significantly more storage-intensive than simply storing metadata (sender, recipient, subject, timestamp). 

    • Potential for Large Storage Footprint:

      • As you correctly pointed out, if you're sending a high volume of emails with attachments or embedded images, the storage requirements can quickly escalate.
      • Your estimate of 50GB per month for half a million emails might even be conservative, depending on the average email size and content. 

    • Compression and Intelligence:

      • While Dynamics 365 and Azure storage services do employ some level of compression, it's unlikely that the "store exact copies" feature implements highly efficient, custom compression algorithms.
      • The primary goal is to preserve the email's fidelity, not to minimize storage at all costs.
      • It is more likely that the emails are stored as blobs of data. 

      •  

    •  

    Factors Affecting Storage Consumption:

    • Email Size:

      • Larger emails with attachments or embedded images consume significantly more storage. 

    • Email Volume:

      • The higher the volume of sent emails, the greater the storage consumption. 

    • Attachment Types and Sizes:

      • Images, PDFs, and other large attachments contribute heavily to storage usage. 

    • HTML Email Complexity:

      • Complex HTML emails with embedded styles and scripts can also increase storage size. 


    •  

    Mitigation and Considerations:

    1. Storage Cost Assessment:

      • Carefully assess the potential storage costs associated with this feature.
      • Use Azure pricing calculators to estimate the cost of storing the anticipated volume of email data. 

    2. Retention Policies:

      • Implement appropriate data retention policies to automatically delete older email copies.
      • This can help control storage growth over time. 

    3. Selective Storage:

      • If possible, explore options to selectively store email copies.
      • For example, you might only store copies of emails sent to specific segments or for specific journey types. 

    4. Monitoring and Reporting:

      • Regularly monitor storage consumption to identify trends and potential issues.
      • Create reports to track email storage usage over time. 

    5. Alternative Storage Solutions:

      • In extreme cases, you might consider alternative storage solutions, such as Azure Blob Storage, and integrate them with Dynamics 365. However, this would require custom development. 

    6. Microsoft Feedback:

      • Provide feedback to Microsoft about the storage implications of this feature.
      • Request more detailed documentation and options for controlling storage consumption. 

    7. Email Size Optimization:

      • If possible, optimize email sizes by compressing images and avoiding unnecessary attachments. 

    8. Testing:

      • Run tests in a none production enviroment, to see how much storage is being used by the feature. 


    9.  

    Key Recommendation:

    • Exercise caution when enabling the "store exact copies of email on timeline" feature, especially in environments with high email volumes.
    • Prioritize storage cost assessment and implement appropriate retention policies.

    •  

    I hope this helps!

     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.
     
    My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.
     
    Regards,
    Daivat Vartak

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,261 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 233,013 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans