There may be scenarios where customers already have an application in production for a product they're looking to automate with PMPC. In the event there is an exact match on the localized app name, PMPC will still be able to create its version of the application with no problem. And it appears this application will also deploy with no problems. But users will run into a console dialog warning them that the application names must be unique if they try to edit either version of the application. With that in mind, there may be underlying reasons Microsoft needs applications to be uniquely named, so for the PMPC import process it might be a good idea to check to see if a non-pmpc app name exists already and either a) skip and log or b) create the app but append to the name to make it unique. In my case, I have appended (PMPC)