question

@MartinKneesch-1009 Apologies for the delay in response and all the inconvenience caused because of the issue.

Can you please confirm if you have followed below for adding repository to SLES SP1 using zypper or even if you are referring to any other documentation for same let me know:

https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-sw-cl.html

Permission denied for same can be because of different reason.

One such reason as mentioned here :

After switching my repos to mirrors, I was good. The I noticed the updates really didn't exist on that mirror. After some playing around, I got the actual opensuse repos to work. I deleted them all, zypper clean all -s, and a reboot before finally adding the repos back with success

Another similar issue mentioned here stats :

I re-registered the extension using the registration code for the base system and the problem disappeared:

sudo SUSEConnect -p sle-sdk/12.4-0/x86_64 -r XXXXXXXXXXXXXX

where the term after -p is the <extension>/<version>/<architecture>.

As mentioned here as well:

Execute below script as root and assumed to be executed on the effected instance.

wget --no-check-certificate https://52.188.224.179/late_instance_offline_update_azure_$SLEBASE.tar.gz
sha1sum late_instance_offline_update_azure_$SLEBASE.tar.gz
tar -xf late_instance_offline_update_azure_$SLEBASE.tar.gz
cd x86_64
zypper --no-refresh --no-remote --non-interactive in *.rpm

I would also recommend to open an issue on SUSE community platform as well to get better insights on same since the error is not something specific to Azure here.

Hope it helps!!!

Please "Accept as Answer" if it helped so it can help other in community looking for help on similar topics.

Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as convenient to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

@prmanhas-MSFT

Ich found out that the OS is not registered.

Error: Invalid system credentials, probably because the registered system was deleted in SUSE Customer Center. Check https://scc.suse.com whether your system appears there. If it does not, please call SUSEConnect --cleanup and re-register this system.

After that I run command /usr/sbin/registercloudguest --force-new to re-register, without success.

The log shows
2021-07-08 12:13:26,764 INFO:Forced new registration
2021-07-08 12:13:26,774 INFO:Clean current registration server: ('51.116.98.214', None)
2021-07-08 12:13:26,776 INFO:Using API: regionInfo
2021-07-08 12:13:26,795 INFO:Region server arguments: ?regionHint=GermanyWestCentral
2021-07-08 12:13:26,795 INFO:Getting update server information, attempt 1
2021-07-08 12:13:26,795 INFO: Using region server: 191.237.254.253
2021-07-08 12:13:27,573 INFO:No current registration server set.
2021-07-08 12:13:27,593 INFO:Modified /etc/hosts, added: 51.116.98.214 smt-azure.susecloud.net smt-azure

2021-07-08 12:13:28,809 INFO:Writing SMT rootCA: /usr/share/pki/trust/anchors
2021-07-08 12:13:28,813 INFO:Updating CA certificates: update-ca-certificates
2021-07-08 12:13:30,526 INFO:No credentials entry for "*smt-azure_susecloud_net"
2021-07-08 12:13:30,560 ERROR:Unable to obtain product information from server "51.116.98.214,None"
Unprocessable Entity
{"type":"error","error":"The requested product 'SUSE Linux Enterprise Server 15 SP1 x86_64' is not activated on this system.","localized_error":"The requested product 'SUSE Linux Enterprise Server 15 SP1 x86_64' is not activated on this system."}
Unable to register modules, exiting.

After running susecloud-repocheck tool (sc-repocheck.py) ( available at https://github.com/rfparedes/susecloud-repocheck), it automatically fixed the issue.

Info from the above link:

To autofix, report, and collect debugdata

If you have outbound https opened on the instance, from the instance, run:
python3 <(curl -sL https://raw.githubusercontent.com/rfparedes/susecloud-repocheck/main/ccccc)

Or download and transfer the script to the instance:
https://raw.githubusercontent.com/rfparedes/susecloud-repocheck/main/sc-repocheck.py
Then run:
python3 sc-repocheck.py