---
updatedAt: 2026-03-01T18:58:48.000Z
agentTools:
  siteIndex: https://techdocs.akamai.com/llms.txt
  projectIndex: https://techdocs.akamai.com/adaptive-media-delivery/llms.txt
---

# Known limitations with MMC

Mixed Mode Configuration (MMC) lets you reuse the various use case-based behaviors to implement several different scenarios. There are some limitations to its use.

<table>

<caption>

</caption>

<colgroup>

<col>

<col>

</colgroup>

<thead>

<tr>

<th>Limitation</th>

<th>Detail</th>

</tr>

</thead>

<tbody>

<tr>

<td><strong>You can only include the Origin Characteristics behavior if Origin Server is also in the rule</strong>.</td>

<td>Since the Default Rule applies to all requests, settings in its instance of the Origin Characteristics behavior must be used. You can't have a unique instance of this behavior in a subsequent rule to apply settings for unique requests. Origin Characteristics must apply to the same Origin Server called out in a rule.</td>

</tr>

<tr>

<td><strong>Signature Header Authentication is not supported in a rule when NetStorage is set as the Origin Type in the Default Rule</strong>.</td>

<td>If you have NetStorage set as your Origin Type in the Default Rule and a custom origin ("Your Origin") set in a subsequent rule, NetStorage authentication header information may be leaked to the custom origin. To avoid this issue, we have disabled the use of Signature Header Auth in rules.</td>

</tr>

<tr>

<td><strong>MMC will not optimize delivery of files that are delivered using another product</strong>.</td>

<td>For example, MMC doesn't optimize delivery of non-segmented media files in your AMD configuration.</td>

</tr>

<tr>

<td><strong>MMC is not supported with AMD through Akamai Cloud Embed (ACE)</strong>.</td>

<td>N/A</td>

</tr>

<tr>

<td><strong>The Watermarking behavior has requirements and known issues that can affect a  Mixed Mode environment</strong>.</td>

<td><p>Consider the following points if you're looking to include the Watermarking feature in your AMD property.</p>

<ul>
<li><strong>Watermarking is currently only supported for use with on-demand media</strong>. If you're applying a Mixed Mode use case for both Media Services Live and other Origin Servers, you'll need to create a separate rule for your non-Media Services Live requests and include the Watermarking behavior in *that rule*. Do not include it in the Default Rule because it applies to all requests.</li>
<li><strong>Prefetching is not recommended</strong>. The current implementation uses an origin-assist model that is not optimal with watermarking. As a result, AMD can't properly apply the Segmented Media Streaming - Prefetch behavior and the Watermarking behavior to a *single request*. Avoid including both behaviors in the same rule. Also, don't apply either behavior in the Default Rule, if the other exists in a subsequent rule in your property. This is because the Default Rule applies to all requests.</li>
</ul>

See <a href="https://techdocs.akamai.com/adaptive-media-delivery/docs/add-wmk" target="_self">How to add Watermarking</a> for more details on this feature.</td>

</tr>

</tbody>

</table>

# Sibling pages

* [Existing properties and MMC](https://techdocs.akamai.com/adaptive-media-delivery/docs/existing-properties-and-mmc.md)
* [Live & on-demand: Different Property Hostnames](https://techdocs.akamai.com/adaptive-media-delivery/docs/live-and-on-demand-different-property-hostnames.md)
* [Live & on-demand: One property hostname, different URL paths](https://techdocs.akamai.com/adaptive-media-delivery/docs/live-on-demand-one-property-hostname-different-url-paths.md)
* [Separate origins using different auth methods](https://techdocs.akamai.com/adaptive-media-delivery/docs/separate-origins-using-different-auth-methods.md)
* [Optimize via different Content Characteristics](https://techdocs.akamai.com/adaptive-media-delivery/docs/optimize-via-different-content-characteristics.md)
* [Optimize via different Client Characteristics](https://techdocs.akamai.com/adaptive-media-delivery/docs/optimize-via-different-client-characteristics.md)