diff --git a/Using-WireMock-in-UnitTests.md b/Using-WireMock-in-UnitTests.md
index 9dc01a1..13349e9 100644
--- a/Using-WireMock-in-UnitTests.md
+++ b/Using-WireMock-in-UnitTests.md
@@ -1,6 +1,6 @@
 # WireMock with your favorite UnitTest framework
 Obviously you can use your favorite test framework and use WireMock.Net within your tests. In order to avoid flaky tests you should:
-  - let WireMock.Net choose ports dynamically. Avoid hard coded ports in your tests.
+  - let WireMock.Net choose ports dynamically. Avoid hard coded ports in your tests. This can cause issues when running these unit-tests on a build-server, there is not 100% guarantee that this port will be free on the OS.
   - clean up the request log or shutdown the server at the end of each test
 
 Below a simple example using Nunit and NFluent test assertion library: