Check is_permutation on a pair of same sized arrays - follow-up
Genericity

Your algorithm currently only works for std::array and nothing else, which is a little bit sad: you could make it work for other sequence containers as well. You could improve this by making you algorithm take two pairs of iterators like the C++14 version of std::is_permutation:

template &lt;typename ForwardIterator1, typename ForwardIterator2&gt;
bool is_permutation(ForwardIterator1 first1, ForwardIterator1 last1,
                    ForwardIterator2 first2, ForwardIterator2 last2);


Note that I used forward iterators since the operations you use do not require anything more specialized to work.

You will have to make some compromises like using std::distance to check whether the sizes are the same, which eventually means that the size comparison will only be \$O(n)\$ for random-access iterators. In a future C++ world with concepts and a standardized std::size, you could have a signature like this:

bool is_permutation(const ForwardIterable&amp; cont1,
                    const ForwardIterable&amp; cont2);


Here, I used the ForwardIterable concept which represents types that have forward iterators. You could then use std::size to compute the size of the container; for std::list, you would have a size in \$O(1)\$ for example while it does not have random-access iterators.

However, we're still stuck in a world without concepts. We can emulate concept constraints but it gets pretty messy, so let's stuck to the iterator version for now even if it means that it won't be optimal.

Smaller concrete things

A few things easy to change that may make you smile:


If you intend to go the genericity way, then use std::begin and std::end instead of the begin and end functions since the former will work on more sequence containers.
These lines could be improved:

if(( myPair.first == first_map.end()) &amp;&amp; (myPair.second == second_map.end()))
    return true;
else
    return false;


First, it's better to always use braces with if and other control structures to avoid small and silent errors in the future. But in this case, you can actually get rid of the condition altogether:

return myPair.first == first_map.end()
    &amp;&amp; myPair.second == second_map.end();

Having to deal with std::pair whenever you want to use std::map and friends can be bothersome. Fortunately, there are ways to hide them. For example, you can change this line:

temp_unordered_map.insert(std::pair&lt;T1,int&gt;(x,1));


into this one:

temp_unordered_map.emplace(x, 1);

The function make_unordered_map does not tell much more than its return type. The name count_occurrences would probably be more suitable and provide more information.
If you plan to keep your function working only for std::array, then you can actually get rid of this runtime check:

if( N1  != N2)


You can replace it by a compile-time static_assert to warn users that they are doing something bad right from the start:

static_assert(N1 == N2, "is_permutation only accepts arrays of the same size");